husted      2003/09/11 16:08:12

  Modified:    doc      releases.xml acquiring.xml
  Log:
  + Routine updates.
  
  Revision  Changes    Path
  1.3       +9 -5      jakarta-struts/doc/releases.xml
  
  Index: releases.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-struts/doc/releases.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- releases.xml      9 Sep 2003 17:49:21 -0000       1.2
  +++ releases.xml      11 Sep 2003 23:08:12 -0000      1.3
  @@ -15,7 +15,7 @@
   
       <p>
       This document describes the Struts <a href="#Releases">release process</a> and 
our <a href="#Coding">coding
  -    conventions</a>.
  +    conventions</a>. Both stable and development releases are <a 
href="acquiring.html">available for download</a>.
       </p>
   
       </section>
  @@ -49,7 +49,8 @@
                   <a 
href="http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases";>Signing a release 
version</a>
                   <ul>
                   <li>
  -                    <small>The MD5 tool is installed on daedalus, and you can 
create the digests for Struts releases there.</small>
  +                    <small>The MD5 tool is installed on daedalus, and you can 
create the digests for Struts releases
  +                        there.</small>
                   </li>
                   </ul>
               </li>
  @@ -64,16 +65,19 @@
   
           <ul>
               <li>
  -                Remember to update the <a href="news/index.html">Status section of 
the News page</a> when cutting any milestone.
  +                Remember to update the <a href="news/index.html">Status section of 
the News page</a> when cutting any
  +                milestone.
                   For a final release, also update the /doc/project.xml with the 
current release number.
               </li>
               <li>
                   The release process can seem daunting when you review it for the 
first time.
                   But, essentially, it breaks down into three phases of just a few 
steps each:
                   <ul>
  -                    <li>Building - Bugzilla, dependencies, release notes, JAR 
manifest, licenses, copyrights, and build (using the release target).</li>
  +                    <li>Building - Bugzilla, dependencies, release notes, JAR 
manifest, licenses, copyrights, and build
  +                        (using the release target).</li>
                       <li>Testing - JUnit, Cactus, web apps (for all "supported" 
containers). </li>
  -                    <li>Distributing - Checksum, sign, mirror, release, update 
Struts site, update Jakarta site, announce.</li>
  +                    <li>Distributing - Checksum, sign, mirror, release, update 
Struts site, update Jakarta site,
  +                        announce.</li>
                   </ul>
               </li>
               <li>
  
  
  
  1.15      +2 -2      jakarta-struts/doc/acquiring.xml
  
  Index: acquiring.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-struts/doc/acquiring.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- acquiring.xml     9 Sep 2003 17:49:21 -0000       1.14
  +++ acquiring.xml     11 Sep 2003 23:08:12 -0000      1.15
  @@ -77,13 +77,13 @@
       
       <li>
           Nightly builds - Download the binary distributions from the
  -       <a href="http://jakarta.apache.org/builds/jakarta-struts/nightly";>
  +       <a href="http://cvs.apache.org/builds/jakarta-struts/nightly";>
           Struts nightly builds directory</a>.
       </li>
       
       <li>
           Nightly builds - Download the source distributions from the
  -        <a href="http://jakarta.apache.org/builds/jakarta-struts/nightly/src";>
  +        <a href="http://cvs.apache.org/builds/jakarta-struts/nightly/src";>
           Struts nightly build source directory</a>.
       </li>
       
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to