ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1300026 - /ant/ivy/core/trunk/doc/dev/makerelease.html
Date Tue, 13 Mar 2012 09:32:42 GMT
Author: hibou
Date: Tue Mar 13 09:32:41 2012
New Revision: 1300026

Update the release process: dist is now under svnpubsub


Modified: ant/ivy/core/trunk/doc/dev/makerelease.html
--- ant/ivy/core/trunk/doc/dev/makerelease.html (original)
+++ ant/ivy/core/trunk/doc/dev/makerelease.html Tue Mar 13 09:32:41 2012
@@ -128,6 +128,13 @@ xooki -r790212
 And commit that modification.
+<h3>Publish the release candidate</h3>
+<ul>Two choices here:
+  <li>commit them into the dev dist area:</li>
+  <li>or simply put it in your <tt>public_html</tt> folder on
so it will be avalaible at$LOGIN/$RELEASENAME</li>
 <h3>13. Call for a vote to approve the release</h3>
 Cast a vote to approve the release on the mailing list.
@@ -148,11 +155,17 @@ Regards,
 ${me}, Ivy ${version} release manager
-<h3>14. Upload to public repository</h3>
-If the release is approved, it's now time to make it public by uploading it to the public
Apache distrib repository (i.e. /www/[version] on people.a.o).
+<h3>14. Publish the release</h3>
+If the release is approved, it's now time to make it public. The apache dist is manage by
svnpubsub, so releases should be committed into
+If the release candidate has been staged into the dev area, then just do:
+$ svn copy$RELEASE_NAME
+$ svn rm$RELEASE_NAME
-Copy also the staging maven 2 repository to apache maven 2 rsync repo:
+If the candidate has been published on, just directly commit the artifacts
into the subversion repository 
 <h3>15. Update the web site</h3>
 Add a link to the released version documentation in the web site. 

View raw message