commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject cvs commit: jakarta-commons/xdocs/releases prepare.xml release.xml
Date Mon, 07 Apr 2003 09:05:07 GMT
rdonkin     2003/04/07 02:05:07

  Modified:    docs/releases prepare.html release.html
               xdocs/releases prepare.xml release.xml
  Log:
  Improved new release how to documentation
  
  Revision  Changes    Path
  1.4       +3 -0      jakarta-commons/docs/releases/prepare.html
  
  Index: prepare.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/docs/releases/prepare.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- prepare.html	29 Mar 2003 10:13:03 -0000	1.3
  +++ prepare.html	7 Apr 2003 09:05:06 -0000	1.4
  @@ -421,6 +421,9 @@
   $ cd $JAKARTA_COMMONS_HOME/foo
   $ cvs tag FOO_1_2
           </pre>
  +                                                <p>
  +        You're now ready to <a href="release.html">cut the release</a>. 
  +        </p>
                               </blockquote>
         </td></tr>
         <tr><td><br/></td></tr>
  
  
  
  1.4       +11 -3     jakarta-commons/docs/releases/release.html
  
  Index: release.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/docs/releases/release.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- release.html	29 Mar 2003 10:13:03 -0000	1.3
  +++ release.html	7 Apr 2003 09:05:07 -0000	1.4
  @@ -268,7 +268,7 @@
   $ cvs -q up -r FOO_1_2
       </pre>
                                                   <p>
  -    Check the build number (to make sure that the update worked correctly).
  +    Check the build number (to make sure that the update worked correctly). This can be
found in the <code>build.xml</code> file.
       </p>
                               </blockquote>
         </td></tr>
  @@ -414,7 +414,8 @@
           <blockquote>
                                       <p>
   OpenPGP (RFC2440) compatible detached signatures needed to be created for all releases.
  -Various applications can be used to create these signatures. For example,
  +Various applications can be used to create these signatures. 
  +For example,
   <a href="http://www.gnupg.org">Gnu Privacy Guard</a> on linux:
       </p>
                                                   <pre>
  @@ -436,6 +437,11 @@
                                                   <p>
   If this is the first release you've cut for this component, then the code signing public
key 
   must be added to the <a href="#Check KEYS file"><code>KEYS</code> file
for the component</a>.
  +This can be found on Daedelus (www.apache.org) at
  +<pre>
  +/www/www.apache.org/dist/jakarta/commons/logging/foo/KEYS
  +</pre>
  +If this file is not present, it needs to be created. 
       </p>
                               </blockquote>
         </td></tr>
  @@ -590,6 +596,8 @@
       The contents of the <code>README.html</code> are displayed at the bottom
of the html 
       showing the directory listing.
       This document should be updated to reflect the new release.
  +    If this document is not present, then copy one from an existing commons mirrored release
directory
  +    and edit that.
   <pre>
   &gt; vi README.html 
   </pre>
  @@ -708,7 +716,7 @@
       </p>
                                                   <ul>
       <li>
  -<strong>Update Jakarta Download Pages'</strong>
  +<strong>Update Jakarta Download Pages</strong>
   Update the Jakarta binary (<code>jakarta-site2/xdocs/site/binindex.xml</code>)
and 
   source (jakarta-site2/<code>xdocs/site/sourceindex.xml</code>) download pages.
   If your component is already listed then you just need to correct the version number.
  
  
  
  1.2       +3 -0      jakarta-commons/xdocs/releases/prepare.xml
  
  Index: prepare.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/xdocs/releases/prepare.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- prepare.xml	11 Mar 2003 22:52:30 -0000	1.1
  +++ prepare.xml	7 Apr 2003 09:05:07 -0000	1.2
  @@ -134,6 +134,9 @@
   $ cd $JAKARTA_COMMONS_HOME/foo
   $ cvs tag FOO_1_2
           </pre>
  +        <p>
  +        You're now ready to <a href='release.html'>cut the release</a>. 
  +        </p>
       </subsection>
     </section>
     
  
  
  
  1.2       +11 -3     jakarta-commons/xdocs/releases/release.xml
  
  Index: release.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/xdocs/releases/release.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- release.xml	11 Mar 2003 22:52:30 -0000	1.1
  +++ release.xml	7 Apr 2003 09:05:07 -0000	1.2
  @@ -55,7 +55,7 @@
   $ cvs -q up -r FOO_1_2
       </pre>
       <p>
  -    Check the build number (to make sure that the update worked correctly).
  +    Check the build number (to make sure that the update worked correctly). This can be
found in the <code>build.xml</code> file.
       </p>
       </subsection>
   
  @@ -156,7 +156,8 @@
   <subsection name='7 Sign Releases'>
       <p>
   OpenPGP (RFC2440) compatible detached signatures needed to be created for all releases.
  -Various applications can be used to create these signatures. For example,
  +Various applications can be used to create these signatures. 
  +For example,
   <a href='http://www.gnupg.org'>Gnu Privacy Guard</a> on linux:
       </p>
   <pre>
  @@ -178,6 +179,11 @@
       <p>
   If this is the first release you've cut for this component, then the code signing public
key 
   must be added to the <a href='#Check KEYS file'><code>KEYS</code> file
for the component</a>.
  +This can be found on Daedelus (www.apache.org) at
  +<pre>
  +/www/www.apache.org/dist/jakarta/commons/logging/foo/KEYS
  +</pre>
  +If this file is not present, it needs to be created. 
       </p>
   </subsection>
   
  @@ -298,6 +304,8 @@
       The contents of the <code>README.html</code> are displayed at the bottom
of the html 
       showing the directory listing.
       This document should be updated to reflect the new release.
  +    If this document is not present, then copy one from an existing commons mirrored release
directory
  +    and edit that.
   <pre>
   > vi README.html 
   </pre>
  @@ -400,7 +408,7 @@
       </p>
       <ul>
       <li>
  -<strong>Update Jakarta Download Pages'</strong>
  +<strong>Update Jakarta Download Pages</strong>
   Update the Jakarta binary (<code>jakarta-site2/xdocs/site/binindex.xml</code>)
and 
   source (jakarta-site2/<code>xdocs/site/sourceindex.xml</code>) download pages.
   If your component is already listed then you just need to correct the version number.
  
  
  

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


Mime
View raw message