cvs commit: jakarta-commons/xdocs releases.xml

2002-09-27 Thread rdonkin 

rdonkin 2002/09/27 14:01:20

  Modified:docs commons.html releases.html
   xdocsreleases.xml
  Log:
  Added some extra tasks to the release jobs list.
  
  Revision  ChangesPath
  1.53  +0 -21 jakarta-commons/docs/commons.html
  
  Index: commons.html
  ===
  RCS file: /home/cvs/jakarta-commons/docs/commons.html,v
  retrieving revision 1.52
  retrieving revision 1.53
  diff -u -r1.52 -r1.53
  --- commons.html  26 Sep 2002 16:08:39 -  1.52
  +++ commons.html  27 Sep 2002 21:01:20 -  1.53
  @@ -201,9 +201,7 @@
 
   
   
  -
   The following proposals for new Commons Proper projects are currently pending :
  -
   
   
   
  @@ -211,44 +209,25 @@
  BeanUtils Package : Craig McClanahan 

   
  -

  -
  Database Connection Pool Package : Rodney Waldhoff
  -

   
  -
  -

  -
  Object Pooling Package : Rodney Waldhoff
  -

   
  -
  -

  -
  Collections Package : Rodney Waldhoff
  -

   
  -
  -

  -
   Cactus, the renamed J2EEUnit : Vincent Massol
  -

   
  -
  -
   
   
  -
   Please see the jakarta-commons mail list for further details.
  -
   
   
   
  
  
  
  1.45  +19 -5 jakarta-commons/docs/releases.html
  
  Index: releases.html
  ===
  RCS file: /home/cvs/jakarta-commons/docs/releases.html,v
  retrieving revision 1.44
  retrieving revision 1.45
  diff -u -r1.44 -r1.45
  --- releases.html 19 Sep 2002 21:04:26 -  1.44
  +++ releases.html 27 Sep 2002 21:01:20 -  1.45
  @@ -265,7 +265,7 @@
   scp commons-foo-1.2-src.* \
 
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
   
  -Please make sure that the files you copy are group writable.
  +Please make sure that the files you copy are group writable.
   
 Follow standard procedures to update the Jakarta web site (stored in
 CVS repository jakarta-site2 to reflect the availability
  @@ -307,7 +307,7 @@
 
 
 
  -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 
foo.xml.  CVS commit, then if you have an account on daedalus, udpate the commons 
website with a cvs udpate in /www/jakarta.apache.org/commons.
  +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 
foo.xml.  CVS commit, then if you have an account on daedalus, update the commons 
website with a cvs udpate in /www/jakarta.apache.org/commons.
   
 Announce the availability of the new package on (at least) the
 following mailing lists:
  @@ -315,9 +315,23 @@
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
  -  
  +  
   
  -
  +Ensure that the pertinent documents in the component's home directory are 
updated to reflect the new release.
  +In particular :
  +
  +In STATUS.html:
  +
  +Update Release Info section
  +Ensure Dependencies is correct
  +Ensure completed tasks are removed from To Do list
  +
  +
  +Update build with new current version
  +
  +
  +Check in bugzilla for all bugs which have been marked LATER and 
update their status appropriately.
  +
   For Collections:
   
   
  @@ -372,7 +386,7 @@
   cvs update
 
   
  -  Follow steps 10-11 above.
  +  Follow steps 10+ above.
 
   
   
  
  
  
  1.9   +19 -5 jakarta-commons/xdocs/releases.xml
  
  Index: releases.xml
  ===
  RCS file: /home/cvs/jakarta-commons/xdocs/releases.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- releases.xml  13 Aug 2002 17:29:33 -  1.8
  +++ releases.xml  27 Sep 2002 21:01:20 -  1.9
  @@ -106,7 +106,7 @@
   scp commons-foo-1.2-src.* \
 
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
   
  -Please make sure that the files you copy are group writable.
  +Please make sure that the files you copy are group writable.
   
 Follow standard procedures to update the Jakarta web site (stored in
 CVS repository jakarta-site2 to reflect the availability
  @@ -148,7 +148,7 @@
 
 
 
  -Update the pertinent documents in the jakar

cvs commit: jakarta-commons/xdocs releases.xml

2002-04-10 Thread morgand 

morgand 02/04/10 10:02:41

  Modified:xdocsreleases.xml
  Log:
  fixed outdated hostnames and email addresses, also added more detail
  abot Collections builds
  
  Revision  ChangesPath
  1.4   +26 -7 jakarta-commons/xdocs/releases.xml
  
  Index: releases.xml
  ===
  RCS file: /home/cvs/jakarta-commons/xdocs/releases.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- releases.xml  28 Mar 2002 18:42:07 -  1.3
  +++ releases.xml  10 Apr 2002 17:02:41 -  1.4
  @@ -36,12 +36,12 @@
   
   
 Announce your proposed release of a particular package to the
  -  [EMAIL PROTECTED] mailing list,
  +  [EMAIL PROTECTED] mailing list,
 and ask for a vote.  Per the Commons Project charter, votes of
 committers on the particular package in question (as listed in the
 STATUS.html file) are binding.
   
  -  Log on to daedalus (via SSH) and create a new subdirectory for the
  +  Log on to jakarta.apache.org (via SSH) and create a new subdirectory for 
the
 release you are about to create.  For example:
   
   cd /www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/
  @@ -90,9 +90,9 @@

[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
   
   
  -  Log in to daedalus and create the source distributions, based on the
  +  Log in to cvs.apache.org and create the source distributions, based on the
 tag specified earlier, and move these files to the distribution
  -  directory as well.  For example,
  +  directory as well.  For example (where "xyz" is your login),
   
   mkdir temp
   cd temp
  @@ -101,8 +101,8 @@
   tar zcvf commons-foo-1.2-src.tar.gz commons-foo-1.2-src
   zip -r commons-foo-1.2-src.zip commons-foo-1.2-src
   rm -rf commons-foo-1.2-src
  -mv commons-foo-1.2-src.* \
  -  /www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
  +scp commons-foo-1.2-src.* \
  +  
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
   
   
 Follow standard procedures to update the Jakarta web site (stored in
  @@ -126,7 +126,7 @@
 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]
  -  [EMAIL PROTECTED]
  +  [EMAIL PROTECTED]
 
   
   
  @@ -166,6 +166,25 @@
   scp RELEASE-NOTES-1.2.html \

[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
   
  +
  +  Update the components.xml and the 
collections.xml
  +  (including the link to the STATUS.html) files.  Run the 
  +  ant command at the root of the jakarta-commons
  +  module, which will build HTML versions of those documents in the 
  +  docs directory.  Check in the generated docs.
  +  
  +  Copy the API docs from the Collections build to the 
  +  jakarta-commons/docs/collections/api directory in CVS.
  +  Be sure to remove Javadocs for any Collections that have been
  +  permanently deleted.
  +  
  +  Log onto jakarta.apache.org and perform a CVS update to grab the new
  +  site documentation:
  +
  +
  +cd /www/jakarta.apache.org/commons/
  +cvs update
  +  
   
 Follow steps 10-11 above.
 
  
  
  

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

cvs commit: jakarta-commons/xdocs releases.xml

2002-03-28 Thread morgand 

morgand 02/03/28 10:42:07

  Modified:xdocsreleases.xml
  Log:
  documented new Collections build
  
  Revision  ChangesPath
  1.3   +42 -0 jakarta-commons/xdocs/releases.xml
  
  Index: releases.xml
  ===
  RCS file: /home/cvs/jakarta-commons/xdocs/releases.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- releases.xml  11 Dec 2001 08:12:04 -  1.2
  +++ releases.xml  28 Mar 2002 18:42:07 -  1.3
  @@ -30,6 +30,8 @@
   of a Commons library package.  The example text consistently
   assumes that we are releasing version 1.2 of the foo
   package.
  +
  +For components other than Collections:
   
   
   
  @@ -128,7 +130,47 @@
 
   
   
  +
  +For Collections:
  +
  +
  +
  +  Follow steps 1-5 above.
  +  
  +  Review the build.xml file to make sure that the "cvs.tag" 
  +  property is set correctly.  For example,
  +  
  +
  +
   
  +  Review the build.properties file to make sure that the 
  +  "cvs.root" property is set correctly.  For example,
  +
  +## in build.properties where "xyz" is your login
  +cvs.root=:pserver:xyz@localhost:/home/cvs
  +
  +  
  +  From the component directory, run ant clean dist dist-src.
  +  
  +  Upload the binary distribution files to the newly created directory
  +  on daedalus.  For example (where "xyz" is your login),
  +
  +cd $JAKARTA_COMMONS_HOME/foo/dist
  +scp commons-foo-1.2* \
  + 
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
  +
  +
  +  Copy the release notes to daedalus.  For example (where "xyz" is your 
login),
  +
  +cd $JAKARTA_COMMONS_HOME/foo/dist
  +scp RELEASE-NOTES-1.2.html \
  + 
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
  +
  +
  +  Follow steps 10-11 above.
  +  
  +
  +  
 
   

  
  
  

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