You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by hi...@apache.org on 2012/03/13 11:35:44 UTC

svn commit: r1300060 - /ant/core/trunk/ReleaseInstructions

Author: hibou
Date: Tue Mar 13 10:35:44 2012
New Revision: 1300060

URL: http://svn.apache.org/viewvc?rev=1300060&view=rev
Log:
Update the release process: dist is now under svnpubsub

Modified:
    ant/core/trunk/ReleaseInstructions

Modified: ant/core/trunk/ReleaseInstructions
URL: http://svn.apache.org/viewvc/ant/core/trunk/ReleaseInstructions?rev=1300060&r1=1300059&r2=1300060&view=diff
==============================================================================
--- ant/core/trunk/ReleaseInstructions (original)
+++ ant/core/trunk/ReleaseInstructions Tue Mar 13 10:35:44 2012
@@ -140,12 +140,15 @@ Note: This document was updated in the c
     if at least three PMC members have voted +1 and more +1s than -1s
     have been cast.  The vote will run for a week.
 
-13. Once the vote has passed, create the release directory,
-    something like v1.7.0Beta1, push the release and RELEASE-NOTES files
-    into this directory.  Create a hardlink named README.html
-    that points to the RELEASE-NOTES (or copy over the RELEASE-NOTES file)
-
-    The files should go to /www/www.apache.org/dist/ant/ on people.apache.org.
+13. Once the vote has passed, the distrib artifacts should be published the
+    apache dist. It is managed via svnpubsub so the release should be
+    committed to the subversion repository
+    https://dist.apache.org/repos/dist/release/ant/.
+
+    In order to keep the main dist area of a reasonable size, old releases
+    should be removed. They will disapear from the main dist but will still be
+    available via the archive. To do so, just use the "svn rm" command against
+    the artifacts or folders to remove.
 
 14. Address the available release tags in BugZilla. Create a new tag 1.7.0Beta1.
     If there is a separate main branch, create a 1.8alpha tag.



Re: svn commit: r1300060 - /ant/core/trunk/ReleaseInstructions

Posted by Nicolas Lalevée <ni...@hibnet.org>.
You'll probably noticed that I have not documented the dev area of the dist svn. While writing the doc I realized that due to the current layout of the distrib artifacts in dist, having a staging release in the dev area will be a pain to manage due to the number of svn commands to launch to manipulate it. So I have kept the doc about referencing a staging area on our accounts on people.apache.org.

Nicolas

Le 13 mars 2012 à 11:35, hibou@apache.org a écrit :

> Author: hibou
> Date: Tue Mar 13 10:35:44 2012
> New Revision: 1300060
> 
> URL: http://svn.apache.org/viewvc?rev=1300060&view=rev
> Log:
> Update the release process: dist is now under svnpubsub
> 
> Modified:
>    ant/core/trunk/ReleaseInstructions
> 
> Modified: ant/core/trunk/ReleaseInstructions
> URL: http://svn.apache.org/viewvc/ant/core/trunk/ReleaseInstructions?rev=1300060&r1=1300059&r2=1300060&view=diff
> ==============================================================================
> --- ant/core/trunk/ReleaseInstructions (original)
> +++ ant/core/trunk/ReleaseInstructions Tue Mar 13 10:35:44 2012
> @@ -140,12 +140,15 @@ Note: This document was updated in the c
>     if at least three PMC members have voted +1 and more +1s than -1s
>     have been cast.  The vote will run for a week.
> 
> -13. Once the vote has passed, create the release directory,
> -    something like v1.7.0Beta1, push the release and RELEASE-NOTES files
> -    into this directory.  Create a hardlink named README.html
> -    that points to the RELEASE-NOTES (or copy over the RELEASE-NOTES file)
> -
> -    The files should go to /www/www.apache.org/dist/ant/ on people.apache.org.
> +13. Once the vote has passed, the distrib artifacts should be published the
> +    apache dist. It is managed via svnpubsub so the release should be
> +    committed to the subversion repository
> +    https://dist.apache.org/repos/dist/release/ant/.
> +
> +    In order to keep the main dist area of a reasonable size, old releases
> +    should be removed. They will disapear from the main dist but will still be
> +    available via the archive. To do so, just use the "svn rm" command against
> +    the artifacts or folders to remove.
> 
> 14. Address the available release tags in BugZilla. Create a new tag 1.7.0Beta1.
>     If there is a separate main branch, create a 1.8alpha tag.
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org