maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From denn...@apache.org
Subject svn commit: r571896 - /maven/site/trunk/src/site/apt/developers/release/releasing.apt
Date Sat, 01 Sep 2007 23:20:01 GMT
Author: dennisl
Date: Sat Sep  1 16:20:00 2007
New Revision: 571896

URL: http://svn.apache.org/viewvc?rev=571896&view=rev
Log:
o Sync with the old release process by adding numbers to the different steps.
o Add missing steps.
o Update the section on using the stage plugin.

Modified:
    maven/site/trunk/src/site/apt/developers/release/releasing.apt

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=571896&r1=571895&r2=571896&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/developers/release/releasing.apt (original)
+++ maven/site/trunk/src/site/apt/developers/release/releasing.apt Sat Sep  1 16:20:00 2007
@@ -30,9 +30,9 @@
  following setup in your <<<$HOME/.m2/settings.xml>>> which is a profile
which provides settings for:
  
  * Your GPG passphrase which will be used to sign all artifacts that are released. If you
have no idea what your
-   GPG passphrase is then refer to {{{pmc-release-process.html}this}}.
+   GPG passphrase is then refer to {{{pmc-release-process.html}this document}}.
             
- * The repository that you want to deploy the release to.
+ * The staging repository that you want to deploy the release to.
 
  Here's what your <<<release>>> profile might look like in your <<<$HOME/.m2/settings.xml>>>:
  
@@ -61,15 +61,55 @@
  
 %{snippet|id=release-profile|url=http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml}
 
- All you need to do in order to release are the familiar 
- 
+* The New Steps
+
+ The following steps replace steps 2-7 in the
+ {{{./pmc-release-process.html}old release process}}.
+
+ [[1]] Prepare the release
+
 +-----+
 mvn release:prepare
++-----+
+ 
+ [[2]] Perform the release
 
++-----+
 mvn release:perform
 +-----+
 
-Copying from the staging repo to the production repo
+ [[3]] Propose a vote on the dev list with the closed issues, the issues left,
+ the staging repository and the staging site. For instance:
+
++-----+
+To: "Maven Developers List" <dev@maven.apache.org>
+Subject: [VOTE] Release Maven XXX plugin version 2.1
+
+Hi,
+
+We solved N issues:
+http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=XXX&styleName=Html&version=XXX
+
+There are still a couple of issues left in JIRA:
+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/
+
+Staging site:
+http://people.apache.org/~YOUR_APACHE_USERNAME/maven-XXX-plugin/
+
+Vote open for 72 hours.
+
+[ ] +1
+[ ] +0
+[ ] -1
+
++-----+
+
+ Once a vote is successful, post the result to the dev list and cc the pmc.
+
+ [[4]] Copy from the staging repo to the production repo
 
  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.
@@ -82,20 +122,17 @@
  Here is an example on how to use the stage plugin:
 
 +-----+
-mvn stage:copy -Dsource="http://people.apache.org/~carlos/staging-repo" -Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository"
-Dversion=2.3 -DrepositoryId=apache.releases
+mvn stage:copy -Dsource="http://people.apache.org/~carlos/staging-repo" \
+               -Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository"
\
+               -Dversion=2.3 \
+               -DtargetRepositoryId=apache.releases
 +-----+
 
- <<Note:>> For some reason the <<<repositoryId>>> configuration
parameter doesn't work yet.
- The <<<repositoryId>>> parameter is required if you need the the plugin
to use the server configuration from your settings file (username, password etc.).
- The <<<version>>> parameter seems to be ignored and the <<entire>>
repository is synced, not just the given version or the current project.
+ <<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.
 
- <<Work-around:>> Until the <<<repositoryId>>> problem has
been solved you can specify your <username> in the target URL like this:
-
-+-----+
-mvn stage:copy -Dsource="http://people.apache.org/~carlos/staging-repo" -Dtarget="scp://myusername@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository"
-Dversion=2.3 -DrepositoryId=apache.releases
-+-----+
-
-Releasing a Project Directly into a Production Repository
+ <<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 point at 
  the production repository by using the following in your <<<$HOME/.m2/settings.xml>>>:
@@ -118,3 +155,10 @@
 
  This will allow you to bypass the staging phase and push the release directly into a production
repository. It is assume that
  you have pushed a snapshot somewhere that people have looked at and approved of.
+
+ [[5]] Deploy the project site
+
+ []
+
+ After that you can continue with step 8 in the
+ {{{./pmc-release-process.html}old release process}}.



Mime
View raw message