commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons/commons-build/xdocs/releases release.xml
Date Sun, 20 Jun 2004 15:21:57 GMT
bayard      2004/06/20 08:21:57

  Modified:    commons-build/xdocs/releases release.xml
  added information about placing jars and poms in the java-repository
  Revision  Changes    Path
  1.12      +19 -6     jakarta-commons/commons-build/xdocs/releases/release.xml
  Index: release.xml
  RCS file: /home/cvs/jakarta-commons/commons-build/xdocs/releases/release.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- release.xml	31 May 2004 13:10:57 -0000	1.11
  +++ release.xml	20 Jun 2004 15:21:57 -0000	1.12
  @@ -392,8 +392,21 @@
  +<subsection name='12 Deploy jar and project.xml to Java-Repository'>
  +    <p>
  +    Your jar file(s) should also be placed in 
  +    <code>/www/</code>.
  +    If available, your project.xml should be placed in 
  +    <code>/www/</code>
  +    as the file <code>commons-foo-1.2.pom</code>. 
  +    Ensure the version number matches the one inside the <code>project.xml</code>.
  +    </p>
  +    <p>
  +    These files will then be mirrored to the iBiblio java repository and picked up by build
  +    </p>
  -<subsection name='12 Test Main Site Downloads'>
  +<subsection name='13 Test Main Site Downloads'>
       You should now be able to get the new release from the main apache web site 
  @@ -419,7 +432,7 @@
  -<subsection name='13 Update Jakarta Web Site'>
  +<subsection name='14 Update Jakarta Web Site'>
   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).

  @@ -475,7 +488,7 @@
  -<subsection name='14 Update Commons Web Site'>
  +<subsection name='15 Update Commons Web Site'>
       <strong>Update Links</strong>.
  @@ -519,7 +532,7 @@
  -<subsection name='15 Create Announcements'>
  +<subsection name='16 Create Announcements'>
   Announce the availability of the new release. 
   You can probably use the news item create earlier as a basis for the announcement body.
  @@ -540,7 +553,7 @@
  -<subsection name='16 Post Release Update'>
  +<subsection name='17 Post Release Update'>
   That's it! The release is out there - but there is still some tidying up to be done.
  @@ -570,7 +583,7 @@
  -<subsection name='17 Update bugzilla'>
  +<subsection name='18 Update bugzilla'>
   Check in bugzilla for all bugs which have been marked <code>LATER</code> and
reopen them. 
   If you need some changes made to bugzilla (for example, a new version number adding) 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message