ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hi...@apache.org
Subject svn commit: r787252 - in /ant/ivy/core/trunk/doc/dev: makerelease.html updatesite.html
Date Mon, 22 Jun 2009 14:40:13 GMT
Author: hibou
Date: Mon Jun 22 14:40:12 2009
New Revision: 787252

URL: http://svn.apache.org/viewvc?rev=787252&view=rev
Log:
We should tag before voting for the release

Modified:
    ant/ivy/core/trunk/doc/dev/makerelease.html
    ant/ivy/core/trunk/doc/dev/updatesite.html

Modified: ant/ivy/core/trunk/doc/dev/makerelease.html
URL: http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/dev/makerelease.html?rev=787252&r1=787251&r2=787252&view=diff
==============================================================================
--- ant/ivy/core/trunk/doc/dev/makerelease.html (original)
+++ ant/ivy/core/trunk/doc/dev/makerelease.html Mon Jun 22 14:40:12 2009
@@ -131,7 +131,15 @@
 
 To be able to test the release within IvyDE, it can be deployed in the IvyDE update site.
See <a href="updatesite.html">that page</a> to know how to process.
 
-<h3>12. Call for a vote to approve the release</h3>
+<h3>12. Tag the svn repository</h3>
+As soon as you are happy with the artifacts to be released, it is time to tag the svn repo
+<code>
+svn copy https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1 \
+           https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.0.0-beta1 \
+      -m "Tag release 2.0.0-beta1."
+</code>
+
+<h3>13. Call for a vote to approve the release</h3>
 Cast a vote to approve the release on the dev@ant.apache.org mailing list.
 
 Here is an example:
@@ -151,13 +159,6 @@
 
 ${me}, Ivy ${version} release manager
 </code>
-<h3>13. Tag the svn repository</h3>
-Now that the release is approved, it is time to tag the svn repo
-<code>
-svn copy https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1 \
-           https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.0.0-beta1 \
-      -m "Tag release 2.0.0-beta1."
-</code>
 <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/www.apache.org/dist/ant/ivy/[version] on people.a.o).
 

Modified: ant/ivy/core/trunk/doc/dev/updatesite.html
URL: http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/dev/updatesite.html?rev=787252&r1=787251&r2=787252&view=diff
==============================================================================
--- ant/ivy/core/trunk/doc/dev/updatesite.html (original)
+++ ant/ivy/core/trunk/doc/dev/updatesite.html Mon Jun 22 14:40:12 2009
@@ -86,6 +86,12 @@
 
 And finally commit your changes.
 
+As soon as you ar happy with the committed artifacts, we can tag the updatesite:
+<pre>
+svn cp https://svn.apache.org/repos/asf/ant/ivy/updatesite/trunk https://svn.apache.org/repos/asf/ant/ivy/updatesite/tags/$TAGNAME
+</pre>
+with <tt>$TAGNAME</tt> the name of the release, so it would be either <tt>ivy-$VERSION</tt>
or <tt>ivyde-$VERSION</tt>.
+
 <h2>Test the updatesite</h2>
 
 The updatesite is ready to be tested. You can deploy it where ever you want with the command:
@@ -99,12 +105,6 @@
 
 <h1><a name="deployment"></a>Deployment of a release</h1>
 
-The release is accepted, so we can tag the updatesite:
-<pre>
-svn cp https://svn.apache.org/repos/asf/ant/ivy/updatesite/trunk https://svn.apache.org/repos/asf/ant/ivy/updatesite/tags/$TAGNAME
-</pre>
-with <tt>$TAGNAME</tt> the name of the release, so it would be either <tt>ivy-$VERSION</tt>
or <tt>ivyde-$VERSION</tt>.
-
 Then backup and deploy. On people.apache.org:
 <pre>
 cd /www/www.apache.org/dist/ant/ivyde/



Mime
View raw message