You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by br...@apache.org on 2009/02/10 05:02:46 UTC
svn commit: r742841 - in /maven/site/trunk/src/site: apt/ apt/developers/
apt/developers/release/ resources/images/ xdoc/
Author: brianf
Date: Tue Feb 10 04:02:45 2009
New Revision: 742841
URL: http://svn.apache.org/viewvc?rev=742841&view=rev
Log:
release process updates
Added:
maven/site/trunk/src/site/resources/images/Close_Repo.png (with props)
maven/site/trunk/src/site/resources/images/Promote.png (with props)
maven/site/trunk/src/site/resources/images/Validate_Artifacts.png (with props)
Modified:
maven/site/trunk/src/site/apt/developers/committer-settings.apt
maven/site/trunk/src/site/apt/developers/release/releasing.apt
maven/site/trunk/src/site/apt/repository-management.apt
maven/site/trunk/src/site/xdoc/articles.xml
Modified: maven/site/trunk/src/site/apt/developers/committer-settings.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/committer-settings.apt?rev=742841&r1=742840&r2=742841&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/developers/committer-settings.apt (original)
+++ maven/site/trunk/src/site/apt/developers/committer-settings.apt Tue Feb 10 04:02:45 2009
@@ -43,8 +43,7 @@
<server>
<id>apache.snapshots</id>
<username> <!-- YOUR APACHE USERNAME --> </username>
- <filePermissions>664</filePermissions>
- <directoryPermissions>775</directoryPermissions>
+ <password> <!-- YOUR APACHE PASSWORD --> </password>
</server>
<!-- To publish a website of some part of Maven -->
<server>
@@ -57,8 +56,7 @@
<server>
<id>apache.releases</id>
<username> <!-- YOUR APACHE USERNAME --> </username>
- <filePermissions>664</filePermissions>
- <directoryPermissions>775</directoryPermissions>
+ <password> <!-- YOUR APACHE PASSWORD --> </password>
</server>
...
</servers>
Modified: maven/site/trunk/src/site/apt/developers/release/releasing.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/release/releasing.apt?rev=742841&r1=742840&r2=742841&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/developers/release/releasing.apt (original)
+++ maven/site/trunk/src/site/apt/developers/release/releasing.apt Tue Feb 10 04:02:45 2009
@@ -3,7 +3,7 @@
-----
Jason van Zyl
-----
- 2008-08-10
+ 2009-02-07
-----
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -51,7 +51,6 @@
<id>release</id>
<properties>
<gpg.passphrase>secretPhrase</gpg.passphrase>
- <deploy.altRepository>apache.releases::default::scp://people.apache.org/home/YOUR_APACHE_USERNAME/staging-repo/maven-XXX-plugin-Y.Z</deploy.altRepository>
</properties>
</profile>
</profiles>
@@ -110,19 +109,9 @@
<<Note:>> You should verify the deployment under Maven Snapshot repository on Apache.
+-----+
-http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/plugins/maven-XXX-plugin/Y.Z-SNAPSHOT/
+https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-XXX-plugin/Y.Z-SNAPSHOT/
+-----+
- [[3]] Run <<<fix-permissions.sh>>>
-
- Login to people.apache.org, then run:
-
-+-----+
-/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
-+-----+
-
- This will set <<<maven-metadata.xml>>> file permissions back to 664, and set permissions on any directories you created to 775.
-
[[4]] Prepare the release
+-----+
@@ -138,7 +127,25 @@
mvn release:perform
+-----+
- [[6]] Stage the latest documentation
+ The release will automatically be inserted into a temporary staging repository for you. See the Nexus {{{http://www.sonatype.com/books/nexus-book/reference/staging.html} staging documentation}} for full details.
+
+ [[6]] Close the staging repository
+
+ Login to {{{https://repository.apache.org}}} using your Apache credentials. Click on "Staging Repositories". Then click on "Maven" in the list of profiles. In the panel below you should see an open repository that is linked to your username and ip. Right click on this repository and select "Finish". This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything.
+
+ See the image below for details.
+
+[../../images/Close_Repo.png] Closing the repository
+
+ [[7]] Verify the Staged artifacts
+
+ Still logged in to {{{https://repository.apache.org}}}, click on "Browse Repositories". Next select the drop down and choose "Nexus Managed Repositories". You will see a list of existing stage repositories. Find yours and then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of .asc (signature) files. If the you don't like the content of the repository, go back to the Staging Repositories screen, right click your repository and choose "Drop". You can then rollback your release and repeat the process.
+
+ Note the repository url, you will need this in your vote email.
+
+[../../images/Validate_Artifacts.png] Validating the artifacts
+
+ [[8]] Stage the latest documentation
The plugin parent POM is configured to stage the documentation in a "versioned" directory
such as <<</plugins/maven-XXX-plugin-Y.Z>>>.
@@ -174,7 +181,7 @@
find . -type f -exec chmod 664 {} \;
+------+
- [[7]] Propose a vote on the dev list with the closed issues, the issues left,
+ [[9]] Propose a vote on the dev list with the closed issues, the issues left,
the staging repository and the staging site. For instance:
+-----+
@@ -190,7 +197,7 @@
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=XXX&status=1
Staging repo:
-http://people.apache.org/~YOUR_APACHE_USERNAME/staging-repo/maven-XXX-plugin-Y.Z
+https://repository.apache.org/content/repositories/maven-staging-[YOUR REPOSITORY ID]/
Staging site:
http://maven.apache.org/plugins/maven-XXX-plugin-Y.Z/
@@ -212,7 +219,7 @@
To get the list of issues left in JIRA, browse to the plugin's JIRA page, and from the <Project Summary>
on the right, use the link for <Open> issues.
- [[8]] Check the vote results
+ [[10]] Check the vote results
Copied from {{{http://www.apache.org/foundation/voting.html}Votes on Package Releases}}.
@@ -241,99 +248,23 @@
+1 (binding): <<list of names>>
+1 (non binding): <<list of names>>
-I will move artifacts to central repo.
+I will promote the artifacts to the central repo.
+-----+
- If the vote is unsuccessful, the process will need to be restarted.
+ If the vote is unsuccessful, the process will need to be restarted. Be sure to drop your staging repository as described above.
- [[9]] Copy from the staging repo to the production repo
+ [[11]] Promote the release
Once the release is deemed fit for public consumption it can be transfered to a production repository where it will
be available to all users.
- Here is an example on how to use the stage plugin:
-
-+-----+
-mvn stage:copy -Dsource="http://people.apache.org/~YOUR_APACHE_USERNAME/staging-repo/maven-XXX-plugin-Y.Z" \
- -Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" \
- -Dversion=Y.Z \
- -DtargetRepositoryId=apache.releases
-+-----+
-
- <<Note:>> The <<<version>>> parameter is currently ignored and the <<entire>>
- staging repository is synced, not just the given version or the current
- project. It still needs to be provided, though.
-
- <<Cleanup>>
-
- Double check there are no *.rip files left after this process.
-
-+-----+
-find /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven -name '*.rip' -ls
-+-----+
-
- And delete any that you own.
+ Login to https://repository.apache.org with your Apache credentials. Click on "Staging Repositories". Find your closed staging repository, right click on it and choose promote. Select the Release repository and click "ok".
- <<TROUBLE SHOOTING>>
+ See image below.
- If you find that stage:copy is hanging at
-
-+-----+
- [INFO] Running rename script on the target machine.
-+-----+
-
- Then this is likely a permission problems.
- Run
-
-+-----+
-find /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven -name '*.rip' -ls
-+-----+
+[../../images/Promote.png] Promote the artifacts
- Then email them the matching users and ask them to run <<<fix-permissions.sh>>>.
-
- (not recommended) <<Releasing a Project Directly into a Production Repository>>
-
- If you want to release directly to a production repository then you simply configure the staging repository to point at
- the production repository by using the following in your <<<$HOME/.m2/settings.xml>>>:
-
-+-----+
-<settings>
- ...
- <profiles>
- <profile>
- <id>release</id>
- <properties>
- <gpg.passphrase>secretPhrase</gpg.passphrase>
- <deploy.altRepository>apache.releases::default::scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository</deploy.altRepository>
- </properties>
- </profile>
- </profiles>
- ...
-</settings>
-+-----+
-
- This will allow you to bypass the staging phase and push the release directly into a production repository. It is assumed that
- you have pushed a snapshot somewhere that people have looked at and approved of.
-
- [[10]] Run <<<fix-permissions.sh>>> again
-
- Login to people.apache.org, then run:
-
-+-----+
-/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
-+-----+
-
- This will once again set <<<maven-metadata.xml>>> file permissions back to 664, and set permissions on any directories you created to 775.
- The script lives in the <<<m2-snapshot-repository>>> directory, but it's smart enough to fix permissions in <<<m2-ibiblio-rsync-repository>>> and <<<m2-incubating-repository>>> also.
-
- [[11]] Deploy the current website
-
- <<Note:>> Be sure to generate and deploy the site using the same version of the release. Typically, you need to check out the tag (or go to <<<target/checkout>>>)
-
-+-----+
-cd target\checkout
-mvn site-deploy -Preporting
-+-----+
+ Next click on Browse Repositories, select the Release repository and validate that your artifacts exist as you expect them.
[[12]] Review the website
Modified: maven/site/trunk/src/site/apt/repository-management.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/repository-management.apt?rev=742841&r1=742840&r2=742841&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/repository-management.apt (original)
+++ maven/site/trunk/src/site/apt/repository-management.apt Tue Feb 10 04:02:45 2009
@@ -55,10 +55,6 @@
Archiva offers several capabilities, amongst which remote repository proxying, security access management, build artifact storage,
delivery, browsing, indexing and usage reporting, extensible scanning functionality... and many more!
-* {{{http://www.pdark.de/dsmp/}Dead Simple Maven Proxy}}
-
- DSMP is a proxy. It can be used as a repository server but it's main purposs it to act as a filter when Maven accesses the internet. If you need a repository server, use Archiva.
-
Why do I need a Repository Manager?
@@ -103,9 +99,9 @@
* Other resources
- * {{{http://www.sonatype.com/book/reference/repository-manager.html#}Chapter on Nexus in Sonatype's <Maven: The Definitive Guide>}}
+ * {{{http://www.sonatype.com/books/nexus-book/reference/}Chapter on Nexus in Sonatype's <Maven: The Definitive Guide>}}
* {{{http://docs.codehaus.org/display/MAVENUSER/Maven+Concepts+Repositories}Maven Concepts Repositories}} from Maven wiki
- *{{{http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix} Continuously updated Feature matrix.}} Superceeds original matrix in the blog below.
+ *{{{http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix} Continuously updated Feature matrix.}}
Added: maven/site/trunk/src/site/resources/images/Close_Repo.png
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/images/Close_Repo.png?rev=742841&view=auto
==============================================================================
Binary file - no diff available.
Propchange: maven/site/trunk/src/site/resources/images/Close_Repo.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: maven/site/trunk/src/site/resources/images/Promote.png
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/images/Promote.png?rev=742841&view=auto
==============================================================================
Binary file - no diff available.
Propchange: maven/site/trunk/src/site/resources/images/Promote.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: maven/site/trunk/src/site/resources/images/Validate_Artifacts.png
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/images/Validate_Artifacts.png?rev=742841&view=auto
==============================================================================
Binary file - no diff available.
Propchange: maven/site/trunk/src/site/resources/images/Validate_Artifacts.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: maven/site/trunk/src/site/xdoc/articles.xml
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/xdoc/articles.xml?rev=742841&r1=742840&r2=742841&view=diff
==============================================================================
--- maven/site/trunk/src/site/xdoc/articles.xml (original)
+++ maven/site/trunk/src/site/xdoc/articles.xml Tue Feb 10 04:02:45 2009
@@ -28,24 +28,24 @@
<body>
<section name="Books on Maven">
<div style="float: left; margin-right: 5em;">
-<a href="http://blogs.sonatype.com/people/book/about/"><img src="images/books/definitive_guide.jpg" title="Maven: The Definitive Guide" /></a>
+<a href="http://www.sonatype.com/books/maven-book/"><img src="images/books/definitive_guide.jpg" title="Maven: The Definitive Guide" /></a>
</div>
<div style="min-height: 220px">
- <p><a href="http://blogs.sonatype.com/people/book/about/"><strong>Maven: The Definitive Guide</strong></a> (Readable HTML and Free PDF Download)</p>
+ <p><a href="http://www.sonatype.com/books/maven-book/"><strong>Maven: The Definitive Guide</strong></a> (Readable HTML and Free PDF Download)</p>
<ul>
<li><strong>Covers: </strong>Maven 2.0.9+</li>
<li><strong>Published: </strong> O'Reilly (Edition 1: October 1, 2008)</li>
<li><strong>Authors: </strong>
<a href="http://www.sonatype.com">Sonatype</a> (
-<a href="http://blogs.sonatype.com/people/jvanzyl">Jason van Zyl</a>,
-<a href="http://blogs.sonatype.com/people/brian">Brian Fox</a>,
-<a href="http://blogs.sonatype.com/people/john">John Casey</a>,
+<a href="http://www.sonatype.com/people/author/jvanzyl">Jason van Zyl</a>,
+<a href="http://www.sonatype.com/people/author/brian">Brian Fox</a>,
+<a href="http://www.sonatype.com/people/author/john">John Casey</a>,
<a href="http://bsnyderblog.blogspot.com/">Bruce Snyder</a>,
-<a href="http://blogs.sonatype.com/people/book">Tim O'Brien</a>,
+<a href="http://www.sonatype.com/people/author/book">Tim O'Brien</a>,
Eric Redmond)
</li>
- <li><strong>Read Online:</strong> <a href="http://blogs.sonatype.com/people/book/about/">http://blogs.sonatype.com/people/book/about/</a></li>
+ <li><strong>Read Online:</strong> <a href="http://www.sonatype.com/books/maven-book/">http://www.sonatype.com/books/maven-book/</a></li>
<li><strong>Buy the Book:</strong> <a href="http://www.amazon.com/Maven-Definitive-Guide-Sonatype-Company/dp/0596517335/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1226091388&sr=8-1">Amazon</a></li>
</ul>
</div>