mbecke 2003/06/03 19:52:23 Modified: httpclient/xdocs releases.xml Log: updated release procedures Revision Changes Path 1.11 +16 -27 jakarta-commons/httpclient/xdocs/releases.xml Index: releases.xml =================================================================== RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/releases.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- releases.xml 26 Feb 2003 19:42:39 -0000 1.10 +++ releases.xml 4 Jun 2003 02:52:23 -0000 1.11 @@ -44,9 +44,9 @@ release.<br/><br/></li> <li>Update the project version number in the <code>build.xml</code>, - <code>project.xml</code>, and the HttpMethodBase useragent string. - There is an Ant property named <code>component.version</code> that would be - updated to <code>2.0</code>. Check in any files you have + <code>project.xml</code>, <code>status.xml</code>, and the HttpMethodBase + useragent string. There is an Ant property named <code>component.version</code> + that would be updated to <code>2.0</code>. Check in any files you have modified.<br/><br/></li> <li>In your local repository (or on cvs.apache.org) tag <strong>only</strong> the @@ -64,7 +64,12 @@ to ensure that it correctly reflects the functionality (and the version number) of this code.<br/><br/></li> - <li>Create a news item. This should be added to httpclient/xdocs/news.xml and + <li>Update release_notes.txt. This file should be updated in CVS when + patches are committed, but it is frequently not. Be sure all relevant + changes since the last release are included. This file should be published + along with the release source and binary distributions.<br/><br/></li> + + <li>Create a news item. This should be added to httpclient/xdocs/news.xml and the jakarta-site2/xdocs/site/news.xml as well as a one liner in jakarta-site2/xdocs/index.html<br/><br/></li> @@ -103,12 +108,6 @@ </pre> NOTE: Make sure that the files you copy are group writable.</li> - <li>Update jakarta-site2 module with the news item in xdocs/site/news.xml - and a one liner in xdocs/index.xml. jakarta-site2 needs to be - checked out from the private cvs. After changes are made run - the build.sh script to generate the site. Browse the generated - html documentation and then commit after you are satisfied.<br/><br/></li> - <li>Follow standard procedures to update the Jakarta web site (stored in CVS repository <code>jakarta-site2</code> to reflect the availability of the new release. Generally, you will be updating the following @@ -123,9 +122,12 @@ <li><code>xdocs/site/news.xml</code> - Create a news item that describes the new release, and includes hyperlinks to the release directory.</li> + <li><code>xdocs/index.xml</code> - Create a one line news item + that links to the full item in site/news.xml.</li> </ul> <ul> <li>Then run ant at the base to generate the new docs and commit the changes to jakarta-site2. + You will be committing the updated xdocs and html. <pre> ant cvs commit -m "update to reflect release of commons-httpclient" @@ -138,9 +140,9 @@ </ul> </li> - <li>Update the pertinent documents in the jakarta-commons/xdocs CVS and then build the - docs by running ant. These pages will probably include components.xml and httpclient.xml. - CVS commit, then if you have an account on daedalus, update the commons website with a + <li>Update components.xml in the jakarta-commons/xdocs CVS and then build the + docs by running ant (this may require some configuration). CVS commit, + then if you have an account on daedalus, update the commons website with a cvs udpate in /www/jakarta.apache.org/commons.<br/></li> <li>Announce the availability of the new package on the following mailing lists: @@ -151,19 +153,6 @@ <li>[EMAIL PROTECTED]</li> </ul><br/></li> - <li>Ensure that the pertinent documents in the component's home directory are updated - to reflect the new release. In particular : - <ul> - <li>In <strong>status.xml</strong>: - <ul> - <li>Update <code>Release Info</code> section</li> - <li>Ensure <code>Dependencies</code> is correct</li> - <li>Ensure completed tasks are removed from <code>To Do</code> list</li> - </ul> - </li> - <li>Update build with new current version</li> - </ul> - <br/></li> <li>Check in bugzilla for all bugs which have been marked <code>LATER</code> and update their status appropriately. If you need to have some changes made to bugzilla you can contact <a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a><br/><br/></li>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]