You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bo...@apache.org on 2008/03/26 21:31:09 UTC
svn commit: r641554 - /ant/core/trunk/ReleaseInstructions
Author: bodewig
Date: Wed Mar 26 13:31:08 2008
New Revision: 641554
URL: http://svn.apache.org/viewvc?rev=641554&view=rev
Log:
update release instructions
Modified:
ant/core/trunk/ReleaseInstructions
Modified: ant/core/trunk/ReleaseInstructions
URL: http://svn.apache.org/viewvc/ant/core/trunk/ReleaseInstructions?rev=641554&r1=641553&r2=641554&view=diff
==============================================================================
--- ant/core/trunk/ReleaseInstructions (original)
+++ ant/core/trunk/ReleaseInstructions Wed Mar 26 13:31:08 2008
@@ -12,13 +12,14 @@
1. Propose a release plan for vote. This should set out the timetable for
the release under ideal circumstances.
- The issue of whether to create a branch for the release should be discussed
- in the release vote.
+ The issue of whether to create a branch for the release should be
+ discussed in the release vote.
- The level of bugs reported can delay things. Generally, give a few weeks to
- "close" the source tree to further changes so people can finalise
- contributions, etc. At this time, the first beta will be cut and there will be
- then a period of beta testing, usually 1 month but this should be flexible.
+ The level of bugs reported can delay things. Generally, give a few
+ weeks to "close" the source tree to further changes so people can
+ finalise contributions, etc. At this time, the first beta will be
+ cut and there will be then a period of beta testing, usually 1
+ month but this should be flexible.
2. Note that any mention of a deadline causes a flood of bug fixes, new tasks,
etc. This needs to be managed as best it can. Some fixes will be applied,
@@ -51,8 +52,8 @@
the first beta on the 1.7 branch has been called 1.7.0Beta1, ...
- the project.version property in build.xml governs the output of ant -version and
- the naming of the distribution files.
+ the project.version property in build.xml governs the output of
+ ant -version and the naming of the distribution files.
Update the following files for version number:
@@ -84,9 +85,10 @@
"Unable to load...".
7. Make sure that your directory tree is clean by running svn status.
- Some tests leave behind leftovers which end up in the source distribution otherwise.
+ Some tests leave behind leftovers which end up in the source
+ distribution otherwise.
-8. Next bootstrap, build and run the tests. Then build the distribution
+8. Next bootstrap, build and run the tests. Then build the distribution
on the branch. It is important that this be a clean build. Label this with
a tag ANT_170_B1.
@@ -109,8 +111,10 @@
see <http://www.gnupg.org/(en)/documentation/faqs.html#q5.5>.
Before you do that, ensure that the key you use is inside the KEYS
- file in Ant's SVN repository - and that you perform a svn update on
- the KEYS file in /www/www.apache.org/dist/ant/
+ file in Ant's SVN repository
+ <https://svn.apache.org/repos/asf/ant/antlibs/common/trunk/KEYS> -
+ and that you perform a svn update on the KEYS file in
+ /www/www.apache.org/dist/ant/common
Also make sure you have sent the key that you use to a public
keyserver.
@@ -128,29 +132,35 @@
Name the generated file RELEASE-NOTES-x.y.z.html.
- Change the title to something like "Release Notes of Apache Ant 1.7.0Beta2" (from the default txt2html)
+ Change the title to something like "Release Notes of Apache Ant
+ 1.7.0Beta2" (from the default txt2html)
[[ TODO: This must perhaps be an Ant task. ]]
-12. Once this is uploaded, unpack things, create the release directory,
+12. Once this is uploaded, unpack things in your home directory
+ and call for a release vote on dev@ant. The vote will only pass
+ 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 symbolic link named README.html
that points to the RELEASE-NOTES.
- The files should go to /www/people.apache.org/dist/ant/ on people.apache.org.
+ The files should go to /www/www.apache.org/dist/ant/ on people.apache.org.
-13. Address the available release tags in BugZilla. Create a new tag 1.7.0Beta1.
+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.
Assign all existing 1.7 alpha bugs to 1.7.0Beta1.
Note that such massive changes can be done at once by choosing the
link "Change several bugs at once" at the bottom of the bug list
displaying the 1.7alpha bugs.
-14. Once that is done, do a test download to make sure everything is OK. A
+15. Once that is done, do a test download to make sure everything is OK. A
common problem may be:
* the file's mime type is not recognized and is interpreted as
text/plain. Fix it by using some .htaccess magic (AddEncoding stuff)
- * Your gz.asc files are not being displayed properly (RemoveEncoing stuff)
+ * Your gz.asc files are not being displayed properly (RemoveEncoding stuff)
If it looks OK, announce it on dev@ant and user@ant. After a few
days pass and there are no major problems, a wider announcement is
@@ -160,34 +170,37 @@
and also perform a svn update on files in people.apache.org's
/www/ant.apache.org/
- you also need to checkout parallel to ant-core https://svn.apache.org/repos/asf/ant/site
- then go to the subdirectory generated
- svn propedit svn:externals to change the location of the manual
+ you also need to checkout parallel to ant-core
+ https://svn.apache.org/repos/asf/ant/site then go to the
+ subdirectory generated svn propedit svn:externals to change the
+ location of the manual
Announce beta releases at freshmeat.net (Stefan Bodewig is the
owner of Ant's project entry - bug him ;-).
-15. As problems in the beta are discovered, there may be a need for
+16. As problems in the beta are discovered, there may be a need for
one or more subsequent betas. The release manager makes this
call. Each time, the versions are updated and the above process is
repeated. Try not to have too many betas.
-16. Try to advertise the need for testing of the betas as much as possible.
+17. Try to advertise the need for testing of the betas as much as possible.
This would eliminate the need to release minor patch versions like
we had to do when releasing Ant 1.4.
To monitor the number of downloads, look at the access_log
file under /usr/local/apache2/logs
-17. When the final beta is considered OK, propose a vote on dev@ant to
+18. When the final beta is considered OK, propose a vote on dev@ant to
officially adopt the latest beta as the Ant 1.6 release. If it is passed,
(it usually does,) this would be labelled ANT_16 and built in a similar
fashion to the above process.
-18. BUT
+ It is probably a good idea to have the re-labeled distribution
+ files ready in time for the vote so that no additional vote on the
+ actual package is required later.
- This time the directory you upload the files to is different and
- you'll have to do some house-keeping for the old release:
+19. This time you'll have to do some house-keeping for the old
+ release:
* upload the new release files to
@@ -210,7 +223,7 @@
(**)
-19. Update the ant.apache.org site :
+20. Update the ant.apache.org site :
running svn update *.html under /www/ant.apache.org should update the
files regenerated and committed in point 5 above (index.html, faq.html,
@@ -218,16 +231,16 @@
Update the online manual too.
-20. Clean up.
+21. Clean up.
- * remove the remaining files of the previous release from
+ * remove the remaining files of the previous release and betas from
/www/www.apache.org/dist/ant/[source|binaries].
This includes the old release notes.
-21. Now and perhaps during previous betas any changes on the branch must
+22. Now and perhaps during previous betas any changes on the branch must
be merged back into the tree.
-22. At this point in time, the release is done and announcements are made.
+23. At this point in time, the release is done and announcements are made.
PGP-sign your announcement posts.
[[TODO: Identify the mailing lists where announcements are to be made.
@@ -243,7 +256,7 @@
Announce release in the usenet groups comp.lang.java.softwaretools
and comp.lang.java.announce.
-23. You can now reacquaint yourself with your family and friends.
+24. You can now reacquaint yourself with your family and friends.
(*) the xdocs need to be updated on both the branch and the HEAD revision
because traditionally the ant.apache.org web site reflects the HEAD
@@ -259,7 +272,7 @@
Related Information
-http://www.apache.org/dev/release-publishing.html
-http://jakarta.apache.org/commons/releases/
-http://wiki.apache.org/jakarta-commons/SigningReleases
+http://www.apache.org/dev/#releases
+http://commons.apache.org/releases/index.html
+http://wiki.apache.org/commons/SigningReleases