jakarta-site-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject cvs commit: jakarta-site2/xdocs/site binindex.xml
Date Mon, 02 Apr 2001 18:36:58 GMT
jon         01/04/02 11:36:58

  Modified:    docs/site binindex.html
               xdocs/site binindex.xml
  Log:
  removed some tomcat specific wording that was based off of the original
  jakarta site.
  
  added Demo Builds to advertise Velocity packaged with Tomcat.
  
  Revision  Changes    Path
  1.37      +12 -9     jakarta-site2/docs/site/binindex.html
  
  Index: binindex.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/docs/site/binindex.html,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- binindex.html	2001/04/02 05:42:20	1.36
  +++ binindex.html	2001/04/02 18:36:54	1.37
  @@ -142,26 +142,29 @@
   <li>Release Builds</li>
   <li>Milestone Builds</li>
   <li>Nightly Builds</li>
  +<li>Demo Builds</li>
   </ul>
                                                   <p>
  -<b>Release Builds</b> are those that are ready for Prime Time. These
  -releases have been reviewed to ensure compatability with the Servlets
  -and JavaServer Pages Specification. This build is "as good as it
  -gets!"
  +<b>Release Builds</b> are those that are ready for Prime Time. This
  +build is "as good as it gets!"
   </p>
                                                   <p>
   <b>Milestone Builds</b> are those that are somewhat stable but not
  -crystal-clean.  We have some confidence in them, but they are buggy
  -and should only be used by advanced users who want to explore future
  -product direction or take advantage of new features. For Tomcat
  -developers, these builds serve as a mechanism to track progress
  -towards a release.
  +crystal-clean.  We have some confidence in them, but they are buggy and
  +should only be used by advanced users who want to explore future product
  +direction or take advantage of new features. For developers, these
  +builds serve as a mechanism to track progress towards a release.
   </p>
                                                   <p>
   <b>Nightly Builds</b> are those that are very unstable
   (a.k.a. dynamite!). We have no confidence in them. They are for
   developers who are helping to develop the technology and want "the
   latest bits." Use at your own risk!
  +</p>
  +                                                <p>
  +<b>Demo Builds</b> are useful for showing demonstrations of our
  +products. For example, we packaged a sample <a href="/velocity/">Velocity</a>
application with a minimal distribution
  +of <a href="/tomcat/">Tomcat</a> 3.x and 4.x.
   </p>
                                                   <p>
   To get the actual source code, <a href="./sourceindex.html">click here</a>.
  
  
  
  1.26      +22 -9     jakarta-site2/xdocs/site/binindex.xml
  
  Index: binindex.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/xdocs/site/binindex.xml,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- binindex.xml	2001/04/02 05:42:20	1.25
  +++ binindex.xml	2001/04/02 18:36:57	1.26
  @@ -25,22 +25,20 @@
   <li>Release Builds</li>
   <li>Milestone Builds</li>
   <li>Nightly Builds</li>
  +<li>Demo Builds</li>
   </ul>
   
   <p>
  -<b>Release Builds</b> are those that are ready for Prime Time. These
  -releases have been reviewed to ensure compatability with the Servlets
  -and JavaServer Pages Specification. This build is "as good as it
  -gets!"
  +<b>Release Builds</b> are those that are ready for Prime Time. This
  +build is "as good as it gets!"
   </p>
   
   <p>
   <b>Milestone Builds</b> are those that are somewhat stable but not
  -crystal-clean.  We have some confidence in them, but they are buggy
  -and should only be used by advanced users who want to explore future
  -product direction or take advantage of new features. For Tomcat
  -developers, these builds serve as a mechanism to track progress
  -towards a release.
  +crystal-clean.  We have some confidence in them, but they are buggy and
  +should only be used by advanced users who want to explore future product
  +direction or take advantage of new features. For developers, these
  +builds serve as a mechanism to track progress towards a release.
   </p>
   
   <p>
  @@ -51,6 +49,13 @@
   </p>
   
   <p>
  +<b>Demo Builds</b> are useful for showing demonstrations of our
  +products. For example, we packaged a sample <a
  +href="/velocity/">Velocity</a> application with a minimal distribution
  +of <a href="/tomcat/">Tomcat</a> 3.x and 4.x.
  +</p>
  +
  +<p>
   To get the actual source code, <a href="./sourceindex.html">click here</a>.
   </p>
   
  @@ -99,6 +104,14 @@
   <li><a href="/builds/jakarta-watchdog/nightly/">Watchdog</a></li>
   </ul>
   </section>
  +
  +<h2>
  +Demo Builds
  +</h2>
  +
  +<ul>
  +<li><a href="/builds/jakarta-velocity/demo/">Velocity 1.0 - ForumDemo</a></li>
  +</ul>
   
   </body>
   </document>
  
  
  

Mime
View raw message