jakarta-site-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hls...@apache.org
Subject svn commit: r154848 [40/41] - in jakarta/site: ./ docs/ docs/site/ docs/site/downloads/ docs/site/news/ docs/site/pmc/ xdocs/ xdocs/downloads/ xdocs/site/news/ xdocs/stylesheets/
Date Tue, 22 Feb 2005 14:05:42 GMT
Modified: jakarta/site/docs/site/roles.html
URL: http://svn.apache.org/viewcvs/jakarta/site/docs/site/roles.html?view=diff&r1=154847&r2=154848
==============================================================================
--- jakarta/site/docs/site/roles.html (original)
+++ jakarta/site/docs/site/roles.html Tue Feb 22 06:03:23 2005
@@ -1,22 +1,18 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 <html>
 <head>
+<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <title>The Jakarta Site - Roles and Responsibilities</title>
-<link type="text/css" href="/style/style.css" rel="stylesheet" />
-<meta value="Apache Jakarta Project" name="author" />
-<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email" />
+<link type="text/css" href="/style/style.css" rel="stylesheet">
+<meta value="Apache Jakarta Project" name="author">
+<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email">
 </head>
 <body>
 <table cellspacing="0" width="100%" border="0" class="page-header">
 <!--PAGE HEADER-->
 <tr>
 <td colspan="2">
-<!--JAKARTA LOGO-->
-<a href="http://jakarta.apache.org/">
-<img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif" />
-</a>
-</td>
+<!--JAKARTA LOGO--><a href="http://jakarta.apache.org/"><img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif"></a></td>
 </tr>
 </table>
 <table cellspacing="4" width="100%" border="0">
@@ -26,7 +22,8 @@
 <navbar name="lhs">
 
     
-    <p>
+    
+<p>
 <strong>Support</strong>
 </p>
 <ul>
@@ -49,7 +46,8 @@
 <a href="http://jakarta.apache.org/site/faqs.html">FAQs</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Subprojects</strong>
 </p>
 <ul>
@@ -111,7 +109,8 @@
 <a href="../watchdog/index.html">Watchdog</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Incubating</strong>
 </p>
 <ul>
@@ -119,7 +118,8 @@
 <a href="http://incubator.apache.org/projects/agila.html">Agila</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Ex-Jakarta</strong>
 </p>
 <ul>
@@ -151,28 +151,29 @@
 <a href="http://struts.apache.org/">Struts</a>
 </li>
 </ul>
-    </navbar>
+    
+</navbar>
 </td>
-<!--MAIN BODY-->
-<td align="left" valign="top" class="main-body">
+<!--MAIN BODY--><td align="left" valign="top" class="main-body">
 <div class="section">
 <div class="section-header">
-<a name="Roles &amp; Responsibilities">
-<strong>Roles &amp; Responsibilities</strong>
-</a>
+<a name="Roles%20&%20Responsibilities"><strong>Roles &amp; Responsibilities</strong></a>
 </div>
 <p>
 <div class="section-body">
-  <p>
+  
+<p>
   The roles and responsibilities that people can assume in the project
   are based on merit. Everybody can help no matter what their role.
   Those who have been long term or valuable contributors to the project
   obtain the right to vote and commit directly to the source repository.
   </p>
 
-  <h2>Users</h2>
+  
+<h2>Users</h2>
 
-  <p>
+  
+<p>
   Users are the people who use the products of the Project. People in
   this role aren't contributing code, but they are using the products,
   reporting bugs, making feature requests, and such. This is by far
@@ -180,14 +181,17 @@
   reason for the Project.
   </p>
 
-  <p>
+  
+<p>
   When a user starts to contribute code or documentation patches, they
   become a Contributor.
   </p>
 
-  <h2>Contributors</h2>
+  
+<h2>Contributors</h2>
 
-  <p>
+  
+<p>
   Contributors are the people who write code or documentation patches or
   contribute positively to the project in other ways. A volunteer's
   contribution is always recognized. In source code, all volunteers
@@ -195,9 +199,11 @@
   authors for that file.
   </p>
 
-  <h2>Committers</h2>
+  
+<h2>Committers</h2>
 
-  <p>
+  
+<p>
   Contributors who give frequent and valuable contributions to a
   subproject of the Project can have their status promoted to that of
   a "<em>Committer</em>" for that subproject. A Committer
@@ -205,18 +211,21 @@
   rights allowing them to affect the future of the subproject.
   </p>
 
-  <p>
+  
+<p>
   In order for a Contributor to become a Committer, another Committer
   can nominate that Contributor or the Contributor can ask for it.
   </p>
 
-  <p>
+  
+<p>
   Once a Contributor is nominated, all of the Committers for a subproject
   will vote. If there are at least 3 positive votes and no negative
   votes, the Contributor is converted into a Committer and given write
   access to the source code repository for that subproject. 
   </p>
-  <p>
+  
+<p>
   The first stage of the process is that the result of the vote thread should be
   carbon copied to the pmc list by the existing committer who will be executing 
   the required process. An email should be sent to the prospected committer offering
@@ -226,11 +235,13 @@
   <strong>pmc at jakarta.apache.org</strong> (so that the reply will be recorded on that list).
   Note that non-pmc members will need to add a additional <code>reply-to</code> header so that they receive a copy.
   </p>
-  <p>
+  
+<p>
   This is an
   example offer letter:
   </p>
 
+
 <div class="source">
 Dear Contributor,
 
@@ -256,14 +267,16 @@
 The Jakarta Project Management Committee.
 </div>
 
-  <p>
+  
+<p>
   Once a positive acknowledgement has been received, the new Committer should be sent an
   acknowledgement. This acknowledgement is a good time to ask for their preferred 
   ASF user name.
   Here is an example acknowledgement letter.
   </p>
 
-  <div class="source">
+  
+<div class="source">
 Dear Committer,
 
 Thank you for accepting our invitation.
@@ -287,7 +300,8 @@
 
 </div>
 
-  <p>
+  
+<p>
   Once the preferred ASF login name has been received from the new committer, 
   an email should be sent to: <strong>root at apache.org</strong>
   requesting that the account be created. A carbon copy must be sent to the 
@@ -299,29 +313,37 @@
   must be included in the email:
   </p>
 
-  <ul>
-     <li>
+  
+<ul>
+     
+<li>
         The name and email address of the new user.
         (ie: John Smith &lt;john.smith.AT.foo.DOT.com&gt;);
      </li>
-     <li>
+     
+<li>
         Suggested account userid. This is optional
         (ie: jmsith);
      </li>
-     <li>
+     
+<li>
         The project that the user should be given access to
         (ie: Jakarta Foo);
      </li>
-     <li>
+     
+<li>
         The results of the votes. In other words, the names and email
         addresses of the committers who approved the addition;
      </li>
-  </ul>
-  <p>
+  
+</ul>
+  
+<p>
   Here is a template:
   </p>
     
-  <div class="source">
+  
+<div class="source">
     {real name} is a new {project name} committer. Please setup his apache.org account.
   
     Name: {desired apache login}
@@ -331,12 +353,14 @@
     Vote: {url to vote thread on mailing list archive}
   </div>
 
-  <p>
+  
+<p>
   The actual account will not be set up until the Contributor License has been received and filed.
   This may take a few days so please be patient.
   </p>
 
-  <p>
+  
+<p>
   Note 0: If a committer already has an account on the apache.org server
   and the committer needs commit access to additional projects, then all
   that needs to be done is to have the user notify
@@ -346,13 +370,15 @@
   creation.
   </p>
 
-  <p>
+  
+<p>
   Note 1: All committers will be given access to the jakarta-site module
   on request. In other words, committers should be able to update the
   main Jakarta website.
   </p>
 
-  <p>
+  
+<p>
   Note 2: If the module that the committer needs access to is a sub
   module within a project (ie: jakarta-turbine-tdk or
   jakarta-avalon-logkit), it is up to the individual project to
@@ -361,19 +387,23 @@
   vote.
   </p>
 
-  <p>
+  
+<p>
   At times, Committers may go inactive for a variety of reasons. A
   Committer that has been inactive for 6 months or more may lose their
   status as a Committer. Getting access back is as simple as
   re-requesting it on the project's Developer mailing list.
   </p>
 
-  <p>
+  
+<p>
   A list of some of our current Committers can be found in our <a href="./whoweare.html">Project Credits</a>.
   </p>
 
-  <p>
-  <h2>Project Management Committee (PMC)</h2>
+  
+<p>
+  
+<h2>Project Management Committee (PMC)</h2>
   Committers who frequently participate with valuable contributions may
   have their status promoted to that of a "<em>Project Management
   Committee Member</em>". This committee is the official managing
@@ -383,22 +413,25 @@
   approved with a 3/4 majority of the PMC.
   </p>
 
-  <p>
+  
+<p>
   To view the Project Management Committee bylaws, <a href="management.html">
   click here</a>.</p>
 
-  <p>
+  
+<p>
   A list of our current PMC Members can be found in our <a href="./whoweare.html">Project Credits</a>.
   </p>
-  </div>
+  
+</div>
 </p>
 </div>
 </td>
-<!--RIGHT SIDE NAVIGATION-->
-<td nowrap="true" valign="top" class="right-navbar">
+<!--RIGHT SIDE NAVIGATION--><td nowrap="true" valign="top" class="right-navbar">
 <navbar name="rhs">
 
-    <p>
+    
+<p>
 <strong>About Jakarta</strong>
 </p>
 <ul>
@@ -421,7 +454,8 @@
 <a href="http://jakarta.apache.org/site/java_at_apache.html">Java@Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Reference</strong>
 </p>
 <ul>
@@ -453,17 +487,23 @@
 <a href="http://www.apache.org/foundation/thanks.html">Acknowledgements</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Search Jakarta</strong>
 </p>
 <div class="searchbox">
-        <form action="http://www.google.com/search" method="get">
-          <input value="jakarta.apache.org" name="sitesearch" type="hidden" />
-          <input size="10" name="q" id="query" type="text" />
-          <input name="Search" value="Search" type="submit" />
-        </form>
-      </div>
-    <p>
+        
+<form action="http://www.google.com/search" method="get">
+          
+<input value="jakarta.apache.org" name="sitesearch" type="hidden">
+          <input size="10" name="q" id="query" type="text">
+          <input name="Search" value="Search" type="submit">
+        
+</form>
+      
+</div>
+    
+<p>
 <strong>Unaffiliated Links</strong>
 </p>
 <ul>
@@ -480,7 +520,8 @@
 <a href="http://www.planetapache.org/">Planet Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Unaffiliated Translations</strong>
 </p>
 <ul>
@@ -494,20 +535,21 @@
 <a href="http://jakarta.jp/">Jakarta.JP (Japanese)</a>
 </li>
 </ul>
+
 </navbar>
 </td>
 </tr>
 <!--FOOTER SEPARATOR-->
 <tr>
 <td colspan="3">
-<hr size="1" noshade="" />
+<hr size="1" noshade="">
 </td>
 </tr>
 <tr>
 <td colspan="3">
 <div class="page-footer">
 <em>
-        Copyright © 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
+        Copyright &copy; 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
         </em>
 </div>
 </td>

Modified: jakarta/site/docs/site/source.html
URL: http://svn.apache.org/viewcvs/jakarta/site/docs/site/source.html?view=diff&r1=154847&r2=154848
==============================================================================
--- jakarta/site/docs/site/source.html (original)
+++ jakarta/site/docs/site/source.html Tue Feb 22 06:03:23 2005
@@ -1,22 +1,18 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 <html>
 <head>
+<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <title>The Jakarta Site - Source Repositories</title>
-<link type="text/css" href="/style/style.css" rel="stylesheet" />
-<meta value="Apache Jakarta Project" name="author" />
-<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email" />
+<link type="text/css" href="/style/style.css" rel="stylesheet">
+<meta value="Apache Jakarta Project" name="author">
+<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email">
 </head>
 <body>
 <table cellspacing="0" width="100%" border="0" class="page-header">
 <!--PAGE HEADER-->
 <tr>
 <td colspan="2">
-<!--JAKARTA LOGO-->
-<a href="http://jakarta.apache.org/">
-<img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif" />
-</a>
-</td>
+<!--JAKARTA LOGO--><a href="http://jakarta.apache.org/"><img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif"></a></td>
 </tr>
 </table>
 <table cellspacing="4" width="100%" border="0">
@@ -26,7 +22,8 @@
 <navbar name="lhs">
 
     
-    <p>
+    
+<p>
 <strong>Support</strong>
 </p>
 <ul>
@@ -49,7 +46,8 @@
 <a href="http://jakarta.apache.org/site/faqs.html">FAQs</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Subprojects</strong>
 </p>
 <ul>
@@ -111,7 +109,8 @@
 <a href="../watchdog/index.html">Watchdog</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Incubating</strong>
 </p>
 <ul>
@@ -119,7 +118,8 @@
 <a href="http://incubator.apache.org/projects/agila.html">Agila</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Ex-Jakarta</strong>
 </p>
 <ul>
@@ -151,26 +151,26 @@
 <a href="http://struts.apache.org/">Struts</a>
 </li>
 </ul>
-    </navbar>
+    
+</navbar>
 </td>
-<!--MAIN BODY-->
-<td align="left" valign="top" class="main-body">
+<!--MAIN BODY--><td align="left" valign="top" class="main-body">
 <div class="section">
 <div class="section-header">
-<a name="Source Repositories">
-<strong>Source Repositories</strong>
-</a>
+<a name="Source%20Repositories"><strong>Source Repositories</strong></a>
 </div>
 <p>
 <div class="section-body">
-  <p>
+  
+<p>
   The Project's codebase is maintained in shared information
   repositories using CVS on the dev.apache.org machine. Only
   Committers have write access to these repositories. Everyone has
   read access via anonymous CVS.
   </p>
 
-  <p>
+  
+<p>
   All Java Language source code in the repository must be written in
   conformance to the "<a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Code
   Conventions for the Java Programming Language</a>" as published
@@ -179,9 +179,11 @@
   page</a> for links to subproject conventions.
   </p>
 
-  <h2>License</h2>
+  
+<h2>License</h2>
 
-  <p>
+  
+<p>
   All source code committed to the Project's repositories must be
   covered by the 
   <a href="http://www.apache.org/foundation/licence-FAQ.html">Apache License</a> 
@@ -189,7 +191,8 @@
   conditions as the Apache License. 
   </p>
 
-  <p>
+  
+<p>
   Committers should update the copyright notice on the Apache License to 
   include the current year when they revise a source file. If it is 2002, 
   and you revise a source file from 1999, change the copyright notice in 
@@ -199,23 +202,27 @@
   year-round, as needed.
   </p>
 
-  <p>
+  
+<p>
   Any code, document, or binary that is committed to the Project's 
   repositories, but not being donated to the ASF, must be clearly marked as 
   such. All contributors should have a <a href="agreement.html">Contributor 
   License Agreement</a> on  file. 
   </p>
 
-  <p>
+  
+<p>
   Any <a href="jars.html">JAR</a> committed to the Project's repositories 
   <strong>must</strong> be licensed for redistribution. BSD and MPL style 
   licenses are generally fine, but many <a href="jars.html">Sun JARs</a> 
   do not permit redistribution.
   </p>
   
-  <h2>Status Files</h2>
+  
+<h2>Status Files</h2>
 
-  <p>
+  
+<p>
   Each of the Project's active source code repositories contain a file
   named <span class="code">STATUS</span> which is used to keep track
   of the agenda and plans for work within that repository. The status
@@ -226,29 +233,35 @@
   else that may be useful to help the group track progress.
   </p>
 
-  <p>
+  
+<p>
   It is recommended that the active status files are automatically
   posted to the developer mailing lists three times per week.
   </p>
 
-  <h2>Branches</h2>
+  
+<h2>Branches</h2>
 
-  <p>
+  
+<p>
   Groups are allowed to create a branch for release cycles, etc. They
   are expected to merge completely back with the main branch as soon as
   their release cycle is complete. All branches currently in use should
   be documented by the respective projects.
   </p>
 
-  <h2>Changes</h2>
+  
+<h2>Changes</h2>
 
-  <p>
+  
+<p>
   Simple patches to fix bugs can be committed then reviewed. With a
   commit-then-review process, the Committer is trusted to have a high
   degree of confidence in the change.
   </p>
 
-  <p>
+  
+<p>
   Doubtful changes, new features, and large scale overhauls need to be
   discussed before committing them into the repository. Any change
   that affects the semantics of an existing API function, the size of
@@ -256,7 +269,8 @@
   receive consensus approval before being committed.
   </p>
 
-  <p>
+  
+<p>
   Related changes should be committed as a group, or very closely
   together. Half complete projects should never be committed to the
   main branch of a development repository. All code changes must be
@@ -264,7 +278,8 @@
   committed. Also, any unit tests should also pass.
   </p>
 
-  <p>
+  
+<p>
   The current source code tree for a subproject should be capable of
   complete compilation at all times. However, it is sometimes
   impossible for a developer on one platform to avoid breaking some
@@ -273,7 +288,8 @@
   committer must indicate that in the commit message.
   </p>
 
-  <p>
+  
+<p>
   A committed change must be reversed if it is vetoed by one of the
   voting members and the veto conditions cannot be immediately
   satisfied by the equivalent of a "bug fix" commit. The
@@ -281,10 +297,12 @@
   public release.
   </p>  
   
-  <h2>
-<a name="Patches" />Patches</h2>
+  
+<h2>
+<a name="Patches"></a>Patches</h2>
 
-  <p>
+  
+<p>
   When a specific change to a product is proposed for discussion or
   voting on the appropriate development mailing list, or contributed
   as part of a bug report, it should be presented in the form of input
@@ -294,7 +312,8 @@
   in the subject corresponding to the action item for that patch.
   </p>
 
-  <p>
+  
+<p>
   The patch should be created by using the <span class="code">diff
   -u</span> command from the original software file(s) to the modified
   software file(s). It is recommended that you submit patches against 
@@ -303,23 +322,29 @@
   that has already been resolved.
   </p>
 
-  <p>
+  
+<p>
   For example:
   </p>
 
-  <div class="source">
+  
+<div class="source">
   diff -u Main.java.orig Main.java &gt;&gt; patchfile.txt
   </div>
 
-  <p>or (preferred)</p>
+  
+<p>or (preferred)</p>
 
-  <div class="source">
+  
+<div class="source">
   cvs diff -u Main.java &gt;&gt; patchfile.txt
   </div>
 
-  <p>or (Win32)</p>
+  
+<p>or (Win32)</p>
 
-  <p>
+  
+<p>
   You can use <a href="http://www.wincvs.org/">WinCVS</a> for a nice GUI or
   you can install <a href="http://sources.redhat.com/cygwin/">Cygwin</a> which
   will enable you to use the bash shell and also installs a lot of other
@@ -327,20 +352,22 @@
   Unix machine.
   </p>
 
- <p>
+ 
+<p>
 <strong>Note:</strong>
-<br />
+<br>
  If you use <a href="http://www.wincvs.org/">WinCVS</a>, move to 
  <code>[Admin]</code> -&gt; <code>[Command Line]</code> Menu 
- and type: <br />
- <code>cvs diff -u</code>
-<br />
+ and type: <br>
+ 
+<code>cvs diff -u</code>
+<br>
  at <code>[Enter a cvs line command]</code> input field 
  (<code>[Commandline Settings] Tab</code>), 
  while selecting the target directories or files, in order to create 
  unified diffs.
  In other words, <code>[Alt+A]</code>+<code>[Alt+C]</code>+
- <code>[Alt+C]</code> and type "<code>cvs diff -u</code>".<br />
+ <code>[Alt+C]</code> and type "<code>cvs diff -u</code>".<br>
  Also, by adding the full path name of WinCVS-Installed directory to
  "path" environment variables, you can use 
  "cvs diff" command on the checked-out directory
@@ -348,20 +375,23 @@
  via MS-DOS command prompt.
  </p>
 
-  <p>
+  
+<p>
   More detailed instructions for accessing Jakarta's CVS repositories with
   various tools and IDEs, including anonymous access, can be found 
   <a href="./cvsindex.html">here</a>.
   </p>
 
-  <p>
+  
+<p>
   All patches necessary to address an action item should be
   concatencated within a single patch message. If later modification
   to the patch proves necessary, the entire new patch should be posted
   and not just the difference between the two patches.
   </p>
   
-  <p>
+  
+<p>
   If your email client line wraps the patch, consider placing the patch
   file up on a website and sending a message to the development list
   with the URL so that the developers with commit access can download
@@ -369,7 +399,8 @@
   part of a bug report.
   </p>
 
-  <p>
+  
+<p>
   When a patch has been checked into CVS, the person who checked in the
   patch should send a message to the person who sent the patch in as
   well as the mailing list specifying that the patch has been checked
@@ -378,15 +409,16 @@
   to help prevent people from applying the patch at the same time.
   </p>
   
-  </div>
+  
+</div>
 </p>
 </div>
 </td>
-<!--RIGHT SIDE NAVIGATION-->
-<td nowrap="true" valign="top" class="right-navbar">
+<!--RIGHT SIDE NAVIGATION--><td nowrap="true" valign="top" class="right-navbar">
 <navbar name="rhs">
 
-    <p>
+    
+<p>
 <strong>About Jakarta</strong>
 </p>
 <ul>
@@ -409,7 +441,8 @@
 <a href="http://jakarta.apache.org/site/java_at_apache.html">Java@Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Reference</strong>
 </p>
 <ul>
@@ -441,17 +474,23 @@
 <a href="http://www.apache.org/foundation/thanks.html">Acknowledgements</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Search Jakarta</strong>
 </p>
 <div class="searchbox">
-        <form action="http://www.google.com/search" method="get">
-          <input value="jakarta.apache.org" name="sitesearch" type="hidden" />
-          <input size="10" name="q" id="query" type="text" />
-          <input name="Search" value="Search" type="submit" />
-        </form>
-      </div>
-    <p>
+        
+<form action="http://www.google.com/search" method="get">
+          
+<input value="jakarta.apache.org" name="sitesearch" type="hidden">
+          <input size="10" name="q" id="query" type="text">
+          <input name="Search" value="Search" type="submit">
+        
+</form>
+      
+</div>
+    
+<p>
 <strong>Unaffiliated Links</strong>
 </p>
 <ul>
@@ -468,7 +507,8 @@
 <a href="http://www.planetapache.org/">Planet Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Unaffiliated Translations</strong>
 </p>
 <ul>
@@ -482,20 +522,21 @@
 <a href="http://jakarta.jp/">Jakarta.JP (Japanese)</a>
 </li>
 </ul>
+
 </navbar>
 </td>
 </tr>
 <!--FOOTER SEPARATOR-->
 <tr>
 <td colspan="3">
-<hr size="1" noshade="" />
+<hr size="1" noshade="">
 </td>
 </tr>
 <tr>
 <td colspan="3">
 <div class="page-footer">
 <em>
-        Copyright © 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
+        Copyright &copy; 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
         </em>
 </div>
 </td>

Modified: jakarta/site/docs/site/understandingopensource.html
URL: http://svn.apache.org/viewcvs/jakarta/site/docs/site/understandingopensource.html?view=diff&r1=154847&r2=154848
==============================================================================
--- jakarta/site/docs/site/understandingopensource.html (original)
+++ jakarta/site/docs/site/understandingopensource.html Tue Feb 22 06:03:23 2005
@@ -1,22 +1,18 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 <html>
 <head>
+<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <title>The Jakarta Site - Understanding Opensource</title>
-<link type="text/css" href="/style/style.css" rel="stylesheet" />
-<meta value="Apache Jakarta Project" name="author" />
-<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email" />
+<link type="text/css" href="/style/style.css" rel="stylesheet">
+<meta value="Apache Jakarta Project" name="author">
+<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email">
 </head>
 <body>
 <table cellspacing="0" width="100%" border="0" class="page-header">
 <!--PAGE HEADER-->
 <tr>
 <td colspan="2">
-<!--JAKARTA LOGO-->
-<a href="http://jakarta.apache.org/">
-<img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif" />
-</a>
-</td>
+<!--JAKARTA LOGO--><a href="http://jakarta.apache.org/"><img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif"></a></td>
 </tr>
 </table>
 <table cellspacing="4" width="100%" border="0">
@@ -26,7 +22,8 @@
 <navbar name="lhs">
 
     
-    <p>
+    
+<p>
 <strong>Support</strong>
 </p>
 <ul>
@@ -49,7 +46,8 @@
 <a href="http://jakarta.apache.org/site/faqs.html">FAQs</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Subprojects</strong>
 </p>
 <ul>
@@ -111,7 +109,8 @@
 <a href="../watchdog/index.html">Watchdog</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Incubating</strong>
 </p>
 <ul>
@@ -119,7 +118,8 @@
 <a href="http://incubator.apache.org/projects/agila.html">Agila</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Ex-Jakarta</strong>
 </p>
 <ul>
@@ -151,18 +151,17 @@
 <a href="http://struts.apache.org/">Struts</a>
 </li>
 </ul>
-    </navbar>
+    
+</navbar>
 </td>
-<!--MAIN BODY-->
-<td align="left" valign="top" class="main-body">
+<!--MAIN BODY--><td align="left" valign="top" class="main-body">
 <div class="section">
 <div class="section-header">
-<a name="Understanding Opensource">
-<strong>Understanding Opensource</strong>
-</a>
+<a name="Understanding%20Opensource"><strong>Understanding Opensource</strong></a>
 </div>
 <p>
 <div class="section-body">
+
 <p>
 With the opensource system, if you find any deficiency in the project, the
 onus is on you to redress that deficiency. Opensource projects provide you
@@ -173,12 +172,14 @@
 and contribution from the user community.
 </p>
 
+
 <p>
 What that boils down to is, if you see something wrong and do nothing about
 it, the opensource system hasnt failed you, *you* have failed the opensource
 system. 
 </p>
 
+
 <p>
 So if I am missing a needed feature in a project and I do nothing about it, it
 is my own fault for not getting off my lazy arse and taking advantage of the
@@ -192,6 +193,7 @@
 words, fix it! :) 
 </p>
 
+
 <p>
 As a rule marketers count bodies lol. With a proprietary product, if I like
 it, the only way I am allowed to participate in it's improvement is by
@@ -205,6 +207,7 @@
 products future. 
 </p>
 
+
 <p>
 Using <a href="/turbine/">Turbine</a> as an opensource example, its
 continued improvement and success is directly proportional to the user
@@ -216,6 +219,7 @@
 improvements would result.
 </p>
 
+
 <p>
 For the above reason, the "more users" isn't important in opensource, we
 all use <a href="/turbine/">Turbine</a> for our own reasons. But
@@ -223,22 +227,26 @@
 improvement of an opensource project, and in our case <a href="/turbine/">Turbine</a>. Contributing and participating in <a href="/turbine/">Turbine</a> is a commonality we should all share :)
 </p>
 
+
 <p>
 Cameron Riley
-<br />
-<a href="mailto:criley NO SPAM ekmail.com">criley NO SPAM ekmail.com</a>
+<br>
+
+<a href="mailto:criley%20NO%20SPAM%20ekmail.com">criley NO SPAM ekmail.com</a>
+
 </p>
 
 
+
 </div>
 </p>
 </div>
 </td>
-<!--RIGHT SIDE NAVIGATION-->
-<td nowrap="true" valign="top" class="right-navbar">
+<!--RIGHT SIDE NAVIGATION--><td nowrap="true" valign="top" class="right-navbar">
 <navbar name="rhs">
 
-    <p>
+    
+<p>
 <strong>About Jakarta</strong>
 </p>
 <ul>
@@ -261,7 +269,8 @@
 <a href="http://jakarta.apache.org/site/java_at_apache.html">Java@Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Reference</strong>
 </p>
 <ul>
@@ -293,17 +302,23 @@
 <a href="http://www.apache.org/foundation/thanks.html">Acknowledgements</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Search Jakarta</strong>
 </p>
 <div class="searchbox">
-        <form action="http://www.google.com/search" method="get">
-          <input value="jakarta.apache.org" name="sitesearch" type="hidden" />
-          <input size="10" name="q" id="query" type="text" />
-          <input name="Search" value="Search" type="submit" />
-        </form>
-      </div>
-    <p>
+        
+<form action="http://www.google.com/search" method="get">
+          
+<input value="jakarta.apache.org" name="sitesearch" type="hidden">
+          <input size="10" name="q" id="query" type="text">
+          <input name="Search" value="Search" type="submit">
+        
+</form>
+      
+</div>
+    
+<p>
 <strong>Unaffiliated Links</strong>
 </p>
 <ul>
@@ -320,7 +335,8 @@
 <a href="http://www.planetapache.org/">Planet Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Unaffiliated Translations</strong>
 </p>
 <ul>
@@ -334,20 +350,21 @@
 <a href="http://jakarta.jp/">Jakarta.JP (Japanese)</a>
 </li>
 </ul>
+
 </navbar>
 </td>
 </tr>
 <!--FOOTER SEPARATOR-->
 <tr>
 <td colspan="3">
-<hr size="1" noshade="" />
+<hr size="1" noshade="">
 </td>
 </tr>
 <tr>
 <td colspan="3">
 <div class="page-footer">
 <em>
-        Copyright © 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
+        Copyright &copy; 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
         </em>
 </div>
 </td>

Modified: jakarta/site/docs/site/vendors.html
URL: http://svn.apache.org/viewcvs/jakarta/site/docs/site/vendors.html?view=diff&r1=154847&r2=154848
==============================================================================
--- jakarta/site/docs/site/vendors.html (original)
+++ jakarta/site/docs/site/vendors.html Tue Feb 22 06:03:23 2005
@@ -1,22 +1,18 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 <html>
 <head>
+<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <title>The Jakarta Site - Third-Party Support for Jakarta Products</title>
-<link type="text/css" href="/style/style.css" rel="stylesheet" />
-<meta value="Apache Jakarta Project" name="author" />
-<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email" />
+<link type="text/css" href="/style/style.css" rel="stylesheet">
+<meta value="Apache Jakarta Project" name="author">
+<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email">
 </head>
 <body>
 <table cellspacing="0" width="100%" border="0" class="page-header">
 <!--PAGE HEADER-->
 <tr>
 <td colspan="2">
-<!--JAKARTA LOGO-->
-<a href="http://jakarta.apache.org/">
-<img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif" />
-</a>
-</td>
+<!--JAKARTA LOGO--><a href="http://jakarta.apache.org/"><img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif"></a></td>
 </tr>
 </table>
 <table cellspacing="4" width="100%" border="0">
@@ -26,7 +22,8 @@
 <navbar name="lhs">
 
     
-    <p>
+    
+<p>
 <strong>Support</strong>
 </p>
 <ul>
@@ -49,7 +46,8 @@
 <a href="http://jakarta.apache.org/site/faqs.html">FAQs</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Subprojects</strong>
 </p>
 <ul>
@@ -111,7 +109,8 @@
 <a href="../watchdog/index.html">Watchdog</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Incubating</strong>
 </p>
 <ul>
@@ -119,7 +118,8 @@
 <a href="http://incubator.apache.org/projects/agila.html">Agila</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Ex-Jakarta</strong>
 </p>
 <ul>
@@ -151,26 +151,28 @@
 <a href="http://struts.apache.org/">Struts</a>
 </li>
 </ul>
-    </navbar>
+    
+</navbar>
 </td>
-<!--MAIN BODY-->
-<td align="left" valign="top" class="main-body">
+<!--MAIN BODY--><td align="left" valign="top" class="main-body">
 <div class="section">
 <div class="section-header">
-<a name="Third-Party Support">
-<strong>Third-Party Support</strong>
-</a>
+<a name="Third-Party%20Support"><strong>Third-Party Support</strong></a>
 </div>
 <p>
 <div class="section-body">
+
 <p>
+
 <b>This listing is provided as a reference only. No endorsements are
 given or implied. If you would like to be added to or removed from
 this list, please send the <a href="source.html#Patches">appropriate
 change</a> to the <a href="mailto:general@jakarta.apache.org">general@jakarta.apache.org</a>
 mailing list.  Pages linked must specifically cite support for one or
 more Jakarta products.</b>
+
 </p>
+
 <p>
 Is your company thinking of taking "the plunge" into more affordable,
 high-quality, open source software solutions? You're not alone. Are you 
@@ -179,17 +181,17 @@
 developer support or by providing complete solutions based on 
 <a href="http://jakarta.apache.org/">Jakarta</a> products.
 </p>
+
 </div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Developer Support (alphabetical order)">
-<strong>Developer Support (alphabetical order)</strong>
-</a>
+<a name="Developer%20Support%20(alphabetical%20order)"><strong>Developer Support (alphabetical order)</strong></a>
 </div>
 <p>
 <div class="section-body">
+
 <p> 
 Developer Support providers focus on helping end-users or developers 
 solve particular problems with a product, usually involving installation, 
@@ -197,287 +199,449 @@
 questions handled on the volunteer lists, but with a guaranteed, confidential 
 response. 
 </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
 <b>company name/website</b>
-   <ul>
-     <li>brief description (&lt;5x80 char lines)</li>
-     <li>City/State/Country</li>
-     <li>email contact</li>
-    </ul>
-   </li>
-  </ul>
-  </p>
-<hr size="1" noshade="noshade" />
-    <p>
-    <ul>
-      <li>
+   
+<ul>
+     
+<li>brief description (&lt;5x80 char lines)</li>
+     
+<li>City/State/Country</li>
+     
+<li>email contact</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+  
+</p>
+
+<hr size="1" noshade="noshade">
+    
+<p>
+    
+<ul>
+      
+<li>
 <b>3GS LLC</b>
-      <ul>
-      <li>3GS LLC is a national provider of development solutions with expertise in many of the Jakarta opensource projects such as Apache, Tomcat, Struts, JMeter, James, etc.  Contact our support department for more information.</li>
-      <li>USA/Nationwide, NY tri-state area</li>
-      <li>support@3gsllc.com</li>
-      </ul>
-    </li>
-    </ul>
-    </p>
-<hr size="1" noshade="noshade" />
-    <p>
-    <ul>
-      <li>
-<a href="http://www.multitask.com.au/default.html?page=mtSOS">
-<b>Multitask</b>
-</a>
-      <ul>
-      <li>We are providing support services to clients in a variety of Open Source projects including various elements of the Apache Software Foundation's Jakarta project: Struts, Ant, Tomcat, Latka, Maven, Log4J.</li>
-      <li>Sydney AU</li>
-      <li>info at multitask.com.au</li>
-      </ul>
-    </li>
-    </ul>
-    </p>
-<hr size="1" noshade="noshade" />
+      
+<ul>
+      
+<li>3GS LLC is a national provider of development solutions with expertise in many of the Jakarta opensource projects such as Apache, Tomcat, Struts, JMeter, James, etc.  Contact our support department for more information.</li>
+      
+<li>USA/Nationwide, NY tri-state area</li>
+      
+<li>support@3gsllc.com</li>
+      
+</ul>
+    
+</li>
+    
+</ul>
+    
+</p>
+
+<hr size="1" noshade="noshade">
+    
+<p>
+    
+<ul>
+      
+<li>
+<a href="http://www.multitask.com.au/default.html?page=mtSOS"><b>Multitask</b></a>
+      
+<ul>
+      
+<li>We are providing support services to clients in a variety of Open Source projects including various elements of the Apache Software Foundation's Jakarta project: Struts, Ant, Tomcat, Latka, Maven, Log4J.</li>
+      
+<li>Sydney AU</li>
+      
+<li>info at multitask.com.au</li>
+      
+</ul>
+    
+</li>
+    
+</ul>
+    
+</p>
+
+<hr size="1" noshade="noshade">
+
 </div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Complete solution providers (alphabetical order)">
-<strong>Complete solution providers (alphabetical order)</strong>
-</a>
+<a name="Complete%20solution%20providers%20(alphabetical%20order)"><strong>Complete solution providers (alphabetical order)</strong></a>
 </div>
 <p>
 <div class="section-body">
+
 <p>
 Complete Solution providers analyze your businesses areas of needs or take
 on specific projects and provide end-to-end solutions including project 
 management, analysis, and technical expertise.
 </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
 <b>company name/website</b>
-   <ul>
-     <li>brief description (&lt;5x80 char lines)</li>
-     <li>City/State/Country</li>
-     <li>email contact</li>
-    </ul>
-   </li>
-  </ul>
-  </p>
+   
+<ul>
+     
+<li>brief description (&lt;5x80 char lines)</li>
+     
+<li>City/State/Country</li>
+     
+<li>email contact</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+  
+</p>
+
+<p>
+
+<hr size="1" noshade="noshade">
+ 
 <p>
-<hr size="1" noshade="noshade" />
- <p>
-   <ul>
-   <li>
-<a href="http://www.aesgi.com/">
-<b>Applied Engineering Software Group</b>
-</a>
-   <ul>
-     <li>
+   
+<ul>
+   
+<li>
+<a href="http://www.aesgi.com/"><b>Applied Engineering Software Group</b></a>
+   
+<ul>
+     
+<li>
          Applied Engineering Software Group is a national provider of Java Web development solutions using Tomcat, Cocoon2 in the business and scientific world under the Linux OS.  We provide complete solutions for our applications including infrastructure.</li>
-     <li>USA nationally operated.</li>
-     <li>Give a analyst a call at 414-397-9223.</li>
-    </ul>
-  </li>
-  </ul>
-  </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
-<a href="http://www.basebeans.com/">
-<b>baseBeans Engineering</b>
-</a>
-   <ul>
-     <li>Provide on-site mentoring, training, and support analysis, and technical expertise, including project management. Areas include MVC, Struts, WebApps, SQL, etc. More info including Open Standards links and Java news on www.basebeans.com.</li>
-     <li>USA/Nationwide, NY tri-state area</li>
-     <li>sales at baseBeans.com</li>
-    </ul>
-   </li>
-  </ul>
-  </p>
-<hr size="1" noshade="noshade" />
-  <p>
-    <ul>
-   <li>
-<a href="http://www.cafesoft.com/">
-<b>Cafesoft</b>
-</a>
-    <ul>
-     <li>We design and implement secure web applications including web single sign-on and centrally managed, policy-based access control to Apache and Tomcat resources. We use our software toolkit, design patterns, and open source to meet business needs. Our experience includes: Ant, Struts, Lucene, Log4J, JMeter, Tomcat, JBoss, OpenLDAP, and MySQL.</li>
-     <li>San Diego, CA, USA</li>
-     <li>info at cafesoft dot com</li>
-    </ul>
-   </li>
-   </ul>
- </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
-<a href="http://www.JAMMConsulting.com/">
-<b>JAMM Consulting, Inc.</b>
-</a>
-   <ul>
-     <li>We provide complete web-based business solutions by creating highly interactive websites using Apache Server, Tomcat, and MySQL on Linux.</li>
-     <li>USA/Nationwide; Dallas-Ft.Worth metropolitan area</li>
-     <li>info at JAMMConsulting.com or call us at (972) 612-6056</li>
-    </ul>
-   </li>
-  </ul>
- </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
-<a href="http://www.openinput.com/">
-<b>OPEN input</b>
-</a>
-   <ul>
-    <li>OPEN input is a company specialized in providing information technologies services related to open source technologies. Our areas of expertise include project mentoring, development and management, training and consultancy. We have experience using Ant, Maven, Struts, Tapestry, Apache httpd and Tomcat, among other open source products.</li>
-    <li>Barcelona, Spain</li>
-    <li>info at openinput dot com</li>
-   </ul>
-   </li>
-  </ul>
- </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
-<a href="http://www.owal.co.uk/2002/owalopensourcepackages.html">
-<b>OpenWeb Analysts Ltd</b>
-</a>
-   <ul>
-     <li>OpenWeb Analysts Ltd solves problems through software. We specialise in making the most of Open Source software in web situations. Whether that is working with a perl based content management system, or writing Java code for an XML/XSLT based document generation system, OpenWeb Analysts has the skills.</li>
-     <li>London, UK</li>
-     <li>info at OWAL.co.uk</li>
-    </ul>
-   </li>
-  </ul>
-  </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
-<a href="http://www.sonogroup.com/">
-<b>The Sono Group, Inc.</b>
-</a>
-   <ul>
-     <li>
+     
+<li>USA nationally operated.</li>
+     
+<li>Give a analyst a call at 414-397-9223.</li>
+    
+</ul>
+  
+</li>
+  
+</ul>
+  
+</p>
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
+<a href="http://www.basebeans.com/"><b>baseBeans Engineering</b></a>
+   
+<ul>
+     
+<li>Provide on-site mentoring, training, and support analysis, and technical expertise, including project management. Areas include MVC, Struts, WebApps, SQL, etc. More info including Open Standards links and Java news on www.basebeans.com.</li>
+     
+<li>USA/Nationwide, NY tri-state area</li>
+     
+<li>sales at baseBeans.com</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+  
+</p>
+
+<hr size="1" noshade="noshade">
+  
+<p>
+    
+<ul>
+   
+<li>
+<a href="http://www.cafesoft.com/"><b>Cafesoft</b></a>
+    
+<ul>
+     
+<li>We design and implement secure web applications including web single sign-on and centrally managed, policy-based access control to Apache and Tomcat resources. We use our software toolkit, design patterns, and open source to meet business needs. Our experience includes: Ant, Struts, Lucene, Log4J, JMeter, Tomcat, JBoss, OpenLDAP, and MySQL.</li>
+     
+<li>San Diego, CA, USA</li>
+     
+<li>info at cafesoft dot com</li>
+    
+</ul>
+   
+</li>
+   
+</ul>
+ 
+</p>
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
+<a href="http://www.JAMMConsulting.com/"><b>JAMM Consulting, Inc.</b></a>
+   
+<ul>
+     
+<li>We provide complete web-based business solutions by creating highly interactive websites using Apache Server, Tomcat, and MySQL on Linux.</li>
+     
+<li>USA/Nationwide; Dallas-Ft.Worth metropolitan area</li>
+     
+<li>info at JAMMConsulting.com or call us at (972) 612-6056</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+ 
+</p>
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
+<a href="http://www.openinput.com/"><b>OPEN input</b></a>
+   
+<ul>
+    
+<li>OPEN input is a company specialized in providing information technologies services related to open source technologies. Our areas of expertise include project mentoring, development and management, training and consultancy. We have experience using Ant, Maven, Struts, Tapestry, Apache httpd and Tomcat, among other open source products.</li>
+    
+<li>Barcelona, Spain</li>
+    
+<li>info at openinput dot com</li>
+   
+</ul>
+   
+</li>
+  
+</ul>
+ 
+</p>
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
+<a href="http://www.owal.co.uk/2002/owalopensourcepackages.html"><b>OpenWeb Analysts Ltd</b></a>
+   
+<ul>
+     
+<li>OpenWeb Analysts Ltd solves problems through software. We specialise in making the most of Open Source software in web situations. Whether that is working with a perl based content management system, or writing Java code for an XML/XSLT based document generation system, OpenWeb Analysts has the skills.</li>
+     
+<li>London, UK</li>
+     
+<li>info at OWAL.co.uk</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+  
+</p>
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
+<a href="http://www.sonogroup.com/"><b>The Sono Group, Inc.</b></a>
+   
+<ul>
+     
+<li>
        We specialize in creating Web-services and custom business workflow 
        solutions using several core components of the Apache Software 
        Foundation's Jakarta project including Tomcat, Struts, Axis and 
        IBM's Websphere.
      </li>
-     <li>San Francisco Bay Area/CA/USA</li>
-     <li>sales@sonogroup.com</li>
-    </ul>
-   </li>
-  </ul>
-  </p>
-<hr size="1" noshade="noshade" />
+     
+<li>San Francisco Bay Area/CA/USA</li>
+     
+<li>sales@sonogroup.com</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+  
+</p>
+
+<hr size="1" noshade="noshade">
+
 <p>
+
+<ul>
+  
+<li>
+<a href="http://www.superlinksoftware.com/"><b>SuperLink Software, Inc.</b></a>
+  
 <ul>
-  <li>
-<a href="http://www.superlinksoftware.com/">
-<b>SuperLink Software, Inc.</b>
-</a>
-  <ul>
-    <li>
+    
+<li>
     providing complete solutions based on Jakarta and <a href="http://xml.apache.org">XML</a> including dynamic Java/XML-based reporting solutions outputting to Microsoft Excel and web applications.  <a href="http://jakarta.apache.org/poi">POI</a> customizations, support and solutions are our specialty!
     </li>
-   <li>Raleigh NC US</li>
-   <li>acoliver at superlinksoftware dot com</li>
-  </ul>
-  </li>
+   
+<li>Raleigh NC US</li>
+   
+<li>acoliver at superlinksoftware dot com</li>
+  
 </ul>
+  
+</li>
+
+</ul>
+
 </p>
-<hr size="1" noshade="noshade" />
-<ul>
-  <li>
-<a href="http://www.tachometry.com/">
-<b>Tachometry</b>
-</a>
-  <ul>
-   <li>
+
+<hr size="1" noshade="noshade">
+
+<ul>
+  
+<li>
+<a href="http://www.tachometry.com/"><b>Tachometry</b></a>
+  
+<ul>
+   
+<li>
  Tachometry is a strategic technology solutions partner for your growing
  business.  Our professional analysis helps us catch hold of your vision,
  then deliver quality software applications based on proven Open Source 
  technologies such as Jakarta Tomcat and Struts. We provide the technology
  you need to grow your business without breaking your budget.
    </li>
-   <li>Walnut Creek, CA, USA - (800) 850-9815</li>
-   <li>info at tachometry dot com</li>
-  </ul>
-  </li>
+   
+<li>Walnut Creek, CA, USA - (800) 850-9815</li>
+   
+<li>info at tachometry dot com</li>
+  
 </ul>
+  
+</li>
+
+</ul>
+
 </p>
-<hr size="1" noshade="noshade" />
- <p>
-  <ul>
-   <li>
-<a href="http://www.xpolog.com/">
-<b>XpoLog Ltd.</b>
-</a>
-   <ul>
-     <li>XpoLog is a Log viewer and analysis server.
+
+<hr size="1" noshade="noshade">
+ 
+<p>
+  
+<ul>
+   
+<li>
+<a href="http://www.xpolog.com/"><b>XpoLog Ltd.</b></a>
+   
+<ul>
+     
+<li>XpoLog is a Log viewer and analysis server.
          XpoLog provides a complete log viewing and support station solution.
          Some of XpoLog 2.2 Features: XML logs, log4j logs - full support,
          Merge logs to one view, Multi Filters for complex filter expressions, 
          Data transformation, Security Architecture based on JAAS and more.    
      </li>
-     <li>Tel-Aviv, Israel</li>
-     <li>marketing@xpolog.com</li>
-    </ul>
-   </li>
-  </ul>
-  </p>
-<hr size="1" noshade="noshade" />
+     
+<li>Tel-Aviv, Israel</li>
+     
+<li>marketing@xpolog.com</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+  
+</p>
+
+<hr size="1" noshade="noshade">
+
 </div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Specialized Solution providers (alphabetical order)">
-<strong>Specialized Solution providers (alphabetical order)</strong>
-</a>
+<a name="Specialized%20Solution%20providers%20(alphabetical%20order)"><strong>Specialized Solution providers (alphabetical order)</strong></a>
 </div>
 <p>
 <div class="section-body">
+
 <p> 
 Specialized Solution providers focus on particular technical areas.
 For instance a Specialized solution provider specializing in Log4J would
 only provide services and consulting for projects directly related to
 Log4J.
 </p>
-<hr size="1" noshade="noshade" />
-  <p>
-  <ul>
-   <li>
+
+<hr size="1" noshade="noshade">
+  
+<p>
+  
+<ul>
+   
+<li>
 <b>company name/website</b>
-   <ul>
-     <li>brief description (&lt;5x80 char lines)</li>
-     <li>City/State/Country</li>
-     <li>email contact</li>
-    </ul>
-   </li>
-  </ul>
-  </p>
-<hr size="1" noshade="noshade" />
+   
+<ul>
+     
+<li>brief description (&lt;5x80 char lines)</li>
+     
+<li>City/State/Country</li>
+     
+<li>email contact</li>
+    
+</ul>
+   
+</li>
+  
+</ul>
+  
+</p>
+
+<hr size="1" noshade="noshade">
+
 </div>
 </p>
 </div>
 </td>
-<!--RIGHT SIDE NAVIGATION-->
-<td nowrap="true" valign="top" class="right-navbar">
+<!--RIGHT SIDE NAVIGATION--><td nowrap="true" valign="top" class="right-navbar">
 <navbar name="rhs">
 
-    <p>
+    
+<p>
 <strong>About Jakarta</strong>
 </p>
 <ul>
@@ -500,7 +664,8 @@
 <a href="http://jakarta.apache.org/site/java_at_apache.html">Java@Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Reference</strong>
 </p>
 <ul>
@@ -532,17 +697,23 @@
 <a href="http://www.apache.org/foundation/thanks.html">Acknowledgements</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Search Jakarta</strong>
 </p>
 <div class="searchbox">
-        <form action="http://www.google.com/search" method="get">
-          <input value="jakarta.apache.org" name="sitesearch" type="hidden" />
-          <input size="10" name="q" id="query" type="text" />
-          <input name="Search" value="Search" type="submit" />
-        </form>
-      </div>
-    <p>
+        
+<form action="http://www.google.com/search" method="get">
+          
+<input value="jakarta.apache.org" name="sitesearch" type="hidden">
+          <input size="10" name="q" id="query" type="text">
+          <input name="Search" value="Search" type="submit">
+        
+</form>
+      
+</div>
+    
+<p>
 <strong>Unaffiliated Links</strong>
 </p>
 <ul>
@@ -559,7 +730,8 @@
 <a href="http://www.planetapache.org/">Planet Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Unaffiliated Translations</strong>
 </p>
 <ul>
@@ -573,20 +745,21 @@
 <a href="http://jakarta.jp/">Jakarta.JP (Japanese)</a>
 </li>
 </ul>
+
 </navbar>
 </td>
 </tr>
 <!--FOOTER SEPARATOR-->
 <tr>
 <td colspan="3">
-<hr size="1" noshade="" />
+<hr size="1" noshade="">
 </td>
 </tr>
 <tr>
 <td colspan="3">
 <div class="page-footer">
 <em>
-        Copyright © 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
+        Copyright &copy; 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
         </em>
 </div>
 </td>

Modified: jakarta/site/docs/site/versioning.html
URL: http://svn.apache.org/viewcvs/jakarta/site/docs/site/versioning.html?view=diff&r1=154847&r2=154848
==============================================================================
--- jakarta/site/docs/site/versioning.html (original)
+++ jakarta/site/docs/site/versioning.html Tue Feb 22 06:03:23 2005
@@ -1,22 +1,18 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
 <html>
 <head>
+<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <title>The Jakarta Site - Versioning Guidelines</title>
-<link type="text/css" href="/style/style.css" rel="stylesheet" />
-<meta value="Apache Jakarta Project" name="author" />
-<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email" />
+<link type="text/css" href="/style/style.css" rel="stylesheet">
+<meta value="Apache Jakarta Project" name="author">
+<meta value="general.AT.jakarta.DOT.apache.DOT.org" name="email">
 </head>
 <body>
 <table cellspacing="0" width="100%" border="0" class="page-header">
 <!--PAGE HEADER-->
 <tr>
 <td colspan="2">
-<!--JAKARTA LOGO-->
-<a href="http://jakarta.apache.org/">
-<img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif" />
-</a>
-</td>
+<!--JAKARTA LOGO--><a href="http://jakarta.apache.org/"><img border="0" alt="The Jakarta Project" src="http://jakarta.apache.org/images/jakarta-logo.gif"></a></td>
 </tr>
 </table>
 <table cellspacing="4" width="100%" border="0">
@@ -26,7 +22,8 @@
 <navbar name="lhs">
 
     
-    <p>
+    
+<p>
 <strong>Support</strong>
 </p>
 <ul>
@@ -49,7 +46,8 @@
 <a href="http://jakarta.apache.org/site/faqs.html">FAQs</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Subprojects</strong>
 </p>
 <ul>
@@ -111,7 +109,8 @@
 <a href="../watchdog/index.html">Watchdog</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Incubating</strong>
 </p>
 <ul>
@@ -119,7 +118,8 @@
 <a href="http://incubator.apache.org/projects/agila.html">Agila</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Ex-Jakarta</strong>
 </p>
 <ul>
@@ -151,86 +151,93 @@
 <a href="http://struts.apache.org/">Struts</a>
 </li>
 </ul>
-    </navbar>
+    
+</navbar>
 </td>
-<!--MAIN BODY-->
-<td align="left" valign="top" class="main-body">
+<!--MAIN BODY--><td align="left" valign="top" class="main-body">
 <div class="section">
 <div class="section-header">
-<a name="Overview">
-<strong>Overview</strong>
-</a>
+<a name="Overview"><strong>Overview</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <p>This document provides:</p>
-   <ul>
-    <li>
+   
+<p>This document provides:</p>
+   
+<ul>
+    
+<li>
      a set of guidelines intended to help project
      teams balance the need to provide a stable interface to
      clients with the growth and evolution of components over
      time,
     </li>
-    <li>
+    
+<li>
      a language for describing the changes to a component
      and the types of incompatibilities such changes may
      create,
     </li>
-    <li>
+    
+<li>
      and a protocol for communicating those changes and
      incompatibilities to users and developers.
     </li>
-   </ul>
-  </div>
+   
+</ul>
+  
+</div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Interface Types">
-<strong>Interface Types</strong>
-</a>
+<a name="Interface%20Types"><strong>Interface Types</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <p>
+   
+<p>
     We identify three distinct categories of interfaces or APIs
     within a component: <em>external</em>, <em>internal</em>
     and <em>private</em>.
    </p>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="The External Interface">
-<strong>The External Interface</strong>
-</a>
+<a name="The%20External%20Interface"><strong>The External Interface</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      The <em>external</em> interface of component is composed of the
      public-facing classes, interfaces, methods and attributes
      provided by the component--those that are likely to be
      used by clients to the component.
     </p>
-    <p>
+    
+<p>
      For obvious reasons, we try to avoid or at least
      acknowledge changes to the external interface.
     </p>
-    <p>
+    
+<p>
      The external interface of a component <em>may</em> correspond to
      the <code>public</code> scope classes and members, but this is not
      always the case. For example, a <code>protected</code> method of a class
      designed to be extended by the clients of a component may
      be deemed part of the external interface.
     </p>
-   </div>
+   
 </div>
-   <div class="subsection">
+</div>
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="The Internal Interface">
-<strong>The Internal Interface</strong>
-</a>
+<a name="The%20Internal%20Interface"><strong>The Internal Interface</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      The <em>internal</em> interface of a component is composed of the
      classes, methods and attributes that are primarily or
      exclusively intended for use by the component
@@ -238,7 +245,8 @@
      unlikely to use or be concerned with the internal
      interface.
     </p>
-    <p>
+    
+<p>
      The internal interface of a component <em>may</em> correspond to
      the <code>package</code> and <code>private</code> scope classes
      and members of the component, but this is not always the case.
@@ -247,56 +255,59 @@
      members, or may, for design reasons, include an interface
      intended primarily for internal use.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="The Private Interface">
-<strong>The Private Interface</strong>
-</a>
+<a name="The%20Private%20Interface"><strong>The Private Interface</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      The <em>private</em> interface of a component is just that--the set
      of classes, methods and attributes that have "package" or
      <code>private</code> scope and hence cannot be used by external clients
      by virtue of the Java Language Specification.
     </p>
-   </div>
+   
+</div>
 </div>
-   <p>
+   
+<p>
     Whenever a class, interface or member is considered part of the
     external or internal interface of a component, it should be
     clearly indicated as such in the JavaDoc comments or other
     documentation for the component. (We may want to consider
     adding custom JavaDoc tags for this purpose.)
    </p>
-  </div>
+  
+</div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Types of Change">
-<strong>Types of Change</strong>
-</a>
+<a name="Types%20of%20Change"><strong>Types of Change</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <p>
+   
+<p>
     We can categorize the changes to a component according to
     the degree to which these changes are compatible with
     previous releases of the component.  We define three such
     categories: <em>fully-compatible</em>, <em>interface-compatible</em>,
     and <em>external-interface-compatible</em>.
    </p>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Fully-Compatible Changes">
-<strong>Fully-Compatible Changes</strong>
-</a>
+<a name="Fully-Compatible%20Changes"><strong>Fully-Compatible Changes</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Release <i>B</i> is said to be <em>fully-compatible</em>
      with Release <i>A</i> if <i>B</i> can simply replace <i>A</i>
      in (<a href="#note1">nearly</a>) all circumstances
@@ -304,78 +315,101 @@
      configuration, and without changing the semantics of any
      <code>public</code> or <code>protected</code> member.
     </p>
-    <p>Examples of fully-compatible changes include:</p>
-    <ul>
-     <li>adding a non-<code>abstract</code> method to a class</li>
-     <li>adding a class or interface to a component</li>
-     <li>
+    
+<p>Examples of fully-compatible changes include:</p>
+    
+<ul>
+     
+<li>adding a non-<code>abstract</code> method to a class</li>
+     
+<li>adding a class or interface to a component</li>
+     
+<li>
       changing a member from <code>private</code> to
       <code>protected</code>
-     </li>
-     <li>
+     
+</li>
+     
+<li>
       changing a <code>private</code> attribute to
       a <code>private</code> method
      </li>
-     <li>
+     
+<li>
       changing an implementation such that a given external
       library is no longer needed by the component
      </li>
-     <li>
+     
+<li>
       changing a method or class from <code>final</code> to
       non-<code>final</code>
-     </li>
-     <li>
+     
+</li>
+     
+<li>
       deprecating, but not otherwise changing, a class, inteface
       or member
      </li>
-     <li>
+     
+<li>
       changing a component in order to fix a defect (a
       deviation from the documented or reasonably expected
       behavior), assuming no other incompatibilities are
       introduced
      </li>
-    </ul>
-    <p>Examples of changes which are not fully-compatible include:</p>
-    <ul>
-     <li>
+    
+</ul>
+    
+<p>Examples of changes which are not fully-compatible include:</p>
+    
+<ul>
+     
+<li>
       a release that no longer supports the same set of JREs,
       or that requires new libraries to be added to the
       classpath
      </li>
-     <li>
+     
+<li>
       changing a <code>public</code> or <code>protected</code> method signature
      </li>
-     <li>
+     
+<li>
       changing the default value of an attribute in a
       behaviour-impacting way
      </li>
-     <li>
+     
+<li>
       removing a class, interface, method or attribute
       from either the internal or external interface of
       the component
      </li>
-    </ul>
-    <p>
+    
+</ul>
+    
+<p>
      Note that not every non-fully-compatible change
      will cause compilation or readily apparent
      run-time problems.
     </p>
-    <p>
+    
+<p>
      Generally speaking, a fully-compatible change will at
      most change the private interface of a component, or simply
      add classes, methods and attributes whose use is optional
      to both internal and external interface clients.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Interface-Compatible Changes">
-<strong>Interface-Compatible Changes</strong>
-</a>
+<a name="Interface-Compatible%20Changes"><strong>Interface-Compatible Changes</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Release <i>B</i> is said to be "interface-compatible" with
      Release <i>A</i> if (<a href="#note1">nearly</a>) all clients
      that can be compiled with <i>A</i> in the classpath can
@@ -384,52 +418,65 @@
      <code>protected</code> member.  A configuration or
      classpath change may be required.
     </p>
-    <p>
+    
+<p>
       Examples of interface-compatible changes include:
     </p>
-    <ul>
-      <li>all fully-compatible changes</li>
-      <li>
+    
+<ul>
+      
+<li>all fully-compatible changes</li>
+      
+<li>
          changing a component such that it now depends
          upon an additional external library or
          configuration file
       </li>
-    </ul>
-    <p>
+    
+</ul>
+    
+<p>
       Examples of changes which are not interface-compatible
       include:
     </p>
-    <ul>
-      <li>
+    
+<ul>
+      
+<li>
          changing a public or protected method signature
       </li>
-      <li>
+      
+<li>
          changing the default value of an attribute in a
          behaviour changing way
       </li>
-      <li>
+      
+<li>
          removing a class, interface, method or attribute
          from either the internal or external interface of the
          component
       </li>
-    </ul>
-    <p>
+    
+</ul>
+    
+<p>
       Generally speaking, an interface-compatible change
       will at most change the private interface of a
       component, or simply add classes, methods and
       attributes whose use is optional to both
       internal and external interface clients.
     </p>
-   </div>
+   
 </div>
-   <div class="subsection">
+</div>
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="External-Interface-Compatible Changes">
-<strong>External-Interface-Compatible Changes</strong>
-</a>
+<a name="External-Interface-Compatible%20Changes"><strong>External-Interface-Compatible Changes</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Release <i>B</i> is said to be "external-interface-compatible"
      with Release <i>A</i> if (<a href="#note1">nearly</a>) all
      clients that depend only on the external interface of a
@@ -439,164 +486,192 @@
      <em>external</em> interface. A configuration or classpath
      change may be required.
     </p>
-    <p>
+    
+<p>
       Examples of external-interface-compatible changes include:
     </p>
-    <ul>
-      <li>all interface-compatible changes</li>
-      <li>
+    
+<ul>
+      
+<li>all interface-compatible changes</li>
+      
+<li>
           removing a class, interface, method or attribute from
           the internal interface of the component
       </li>
-      <li>
+      
+<li>
           a change to the internal or private interface of a
           component that requires a change in configuration
           settings or in the external libraries required to
           use the component
       </li>
-      <li>
+      
+<li>
           changes to the internal or private interface of a
           component without impacting the external interface
       </li>
-    </ul>
-    <p>
+    
+</ul>
+    
+<p>
       Examples of changes which are not
       external-interface-compatible include:
     </p>
-    <ul>
-      <li>
+    
+<ul>
+      
+<li>
         changing the method signature of any method that is
         part of the external interface of the component
       </li>
-      <li>
+      
+<li>
         changing the default value of any attribute that is
         part of the external interface of the component in a
         behaviour changing way
       </li>
-      <li>
+      
+<li>
         removing a class, interface, method or attribute from
         external interface of the component
       </li>
-    </ul>
-    <p>
+    
+</ul>
+    
+<p>
       Generally speaking, external-interface-compatible
       changes correspond to changes to at most the internal
       interface of the component or the addition of
       optional classes, interfaces or members to the
       external interface.
     </p>
-   </div>
+   
+</div>
+</div>
+  
 </div>
-  </div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Release Types">
-<strong>Release Types</strong>
-</a>
+<a name="Release%20Types"><strong>Release Types</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <p>
+   
+<p>
     We identify five types of releases: "Major", "Minor",
     "Point", "Beta" and "Milestone".
    </p>
-   <p>
+   
+<p>
     Developers are encouraged to "upgrade" a release to a
     stronger type whenever the nature or scope of the change
     warrants it.
    </p>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Major Releases">
-<strong>Major Releases</strong>
-</a>
+<a name="Major%20Releases"><strong>Major Releases</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Major releases signify significant changes to a component.
      Developers <em>may</em> perform a major release if there have been
      substantial improvements to the component.  Developers
      <em>must</em> perform a major release whenever the new release
      is not at least interface-compatible the previous release.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Minor Releases">
-<strong>Minor Releases</strong>
-</a>
+<a name="Minor%20Releases"><strong>Minor Releases</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Minor releases signify enhancements to a component that do
      not necessitate a major release.  Developers <em>may</em> perform a
      minor release if the release is at least
      external-interface-compatible with the previous release.
     <p>
-    </p>
+    
+</p>
      In other words, whenever a client depends upon at most
      the external interface of a component with a given minor
      release, it will work with all subsequent minor releases
      within that major release.
     </p>
-   </div>
+   
 </div>
-   <div class="subsection">
+</div>
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Point Releases">
-<strong>Point Releases</strong>
-</a>
+<a name="Point%20Releases"><strong>Point Releases</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      A point release typically involves simple bug fixes or
      optimizations that do not introduce new features.
      Developers <em>may</em> perform a point release if the release
      is at least interface-compatible with the
      previous release.
     </p>
-    <p>
+    
+<p>
      In other words, whenever a client depends upon a component
      with a given point release, it will work with all
      subsequent point releases within that minor release.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Beta Releases">
-<strong>Beta Releases</strong>
-</a>
+<a name="Beta%20Releases"><strong>Beta Releases</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Developers may, at their option, perform a beta preview of
      any major, minor or point release.  Beta releases may be
      performed for a variety of purposes such as:
     </p>
-    <ul>
-     <li>Showcasing new, untested features</li>
-     <li>Providing early corrections of critical bugs</li>
-     <li>Generating a stable version before large-scale changes</li>
-    </ul>
-    <p>
+    
+<ul>
+     
+<li>Showcasing new, untested features</li>
+     
+<li>Providing early corrections of critical bugs</li>
+     
+<li>Generating a stable version before large-scale changes</li>
+    
+</ul>
+    
+<p>
      While every effort should be made to ensure the quality of
      released code, "beta" releases are essentially provided
      as-is with no guarantees of stability or maintenance.
     </p>
-   </div>
+   
 </div>
-   <div class="subsection">
+</div>
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Milestone Releases">
-<strong>Milestone Releases</strong>
-</a>
+<a name="Milestone%20Releases"><strong>Milestone Releases</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Developers may, at their option, offer a milestone
      preview of any major release.  A milestone release is
      appropriate when part of the overall component is
@@ -605,128 +680,142 @@
      remaining to be implemented should be clearly defined and
      documented.
     </p>
-    <p>
+    
+<p>
      While every effort should be made to ensure the quality of
      released code, "milestone" releases are essentially
      provided as-is with no guarantees of stability or
      maintenance.
     </p>
-   </div>
+   
+</div>
+</div>
+  
 </div>
-  </div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Release Numbers">
-<strong>Release Numbers</strong>
-</a>
+<a name="Release%20Numbers"><strong>Release Numbers</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Initial Release Number">
-<strong>Initial Release Number</strong>
-</a>
+<a name="Initial%20Release%20Number"><strong>Initial Release Number</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      A component's initial release number is generally
      1.0[.0], unless there have been versioned beta releases.
     </p>
-   </div>
+   
 </div>
-   <div class="subsection">
+</div>
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Dissecting the Release Number">
-<strong>Dissecting the Release Number</strong>
-</a>
+<a name="Dissecting%20the%20Release%20Number"><strong>Dissecting the Release Number</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      A release number is comprised of 3 components: the major
      release number, the minor release number, and an optional
      point release number.  Here is a sample release number:
     </p>
-    <p>
+    
+<p>
 <code>2.0.4</code>
 </p>
-    <p>and it can be broken into three parts:</p>
-    <ul>
-     <li>major release: 2</li>
-     <li>minor release: 0</li>
-     <li>point release: 4</li>
-    </ul>
-    <p>
+    
+<p>and it can be broken into three parts:</p>
+    
+<ul>
+     
+<li>major release: 2</li>
+     
+<li>minor release: 0</li>
+     
+<li>point release: 4</li>
+    
+</ul>
+    
+<p>
      The next release of this component would increment the
      appropriate part of the release number, depending on the
      type of release (major, minor, or point).  For example, a
      subsequent minor release would be version 2.1, or a
      subsequent major release would be 3.0.
     </p>
-    <p>
+    
+<p>
      Note that release numbers are composed of three _integers_,
      not three <em>digits</em>.  Hence if the current release is
      3.9.4, the next minor release is 3.10.0.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Beta Release Numbers">
-<strong>Beta Release Numbers</strong>
-</a>
+<a name="Beta%20Release%20Numbers"><strong>Beta Release Numbers</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Beta releases are denoted by adding
      "B&lt;beta version number&gt;" after the release number.  For
      example, if the current release version is 2.0.4, and a
      developer wished to preview the next major release, the
      release would be labeled 3.0-B1.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Milestone Release Numbers">
-<strong>Milestone Release Numbers</strong>
-</a>
+<a name="Milestone%20Release%20Numbers"><strong>Milestone Release Numbers</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Beta releases are denoted by adding
      "M&lt;milestone version number&gt;" after the release number.  For
      example, if the current release version is 2.0.4, and a
      developer wished to preview the next major release, the
      release would be labeled 3.0-M1.
     </p>
-   </div>
+   
+</div>
+</div>
+  
 </div>
-  </div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Development States">
-<strong>Development States</strong>
-</a>
+<a name="Development%20States"><strong>Development States</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <p>
+   
+<p>
     We identify four possible states: "in development", "beta",
     "released", and "unsupported".
    </p>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="In Development State">
-<strong>In Development State</strong>
-</a>
+<a name="In%20Development%20State"><strong>In Development State</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
       When a component is "in development", it is new and still
       relatively unstable. Typically components in this state
       do not have any binary releases available beyond the
@@ -737,16 +826,17 @@
       make the features currently implemented more widely
       available for testing in a more stable test version.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Beta State">
-<strong>Beta State</strong>
-</a>
+<a name="Beta%20State"><strong>Beta State</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
       When a component has made significant progress toward
       release-quality code, the committers may vote to perform
       a "beta" release.  At this point, the component state will
@@ -754,21 +844,23 @@
       remain in this state until it is ready for its first major
       release.
     </p>
-    <p>
+    
+<p>
       Note that developers may skip vote to skip the "beta" state
       and go directly to "released", if the component is
       sufficiently stable.
     </p>
-   </div>
+   
 </div>
-   <div class="subsection">
+</div>
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Released State">
-<strong>Released State</strong>
-</a>
+<a name="Released%20State"><strong>Released State</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      When a new component is finally production-quality, the
      developers may vote to perform the first major release.
      At this point, the component status will be changed from
@@ -777,16 +869,17 @@
      when new releases are initiated. The only exception is in
      the case of "unsupported" components.
     </p>
-   </div>
+   
+</div>
 </div>
-   <div class="subsection">
+   
+<div class="subsection">
 <div class="subsection-header">
-<a name="Unsupported State">
-<strong>Unsupported State</strong>
-</a>
+<a name="Unsupported%20State"><strong>Unsupported State</strong></a>
 </div>
 <div class="subsection-body">
-    <p>
+    
+<p>
      Under rare circumstances, committers may vote to make a
      component "unsupported", if there are no resources to
      maintain the library or if it has been completely
@@ -795,25 +888,27 @@
      states will simply be terminated after a brief warning
      period.
     </p>
-   </div>
+   
+</div>
+</div>
+  
 </div>
-  </div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="Comments">
-<strong>Comments</strong>
-</a>
+<a name="Comments"><strong>Comments</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <p>
+   
+<p>
       Using this approach it is possible to very precisely and
       concisely define the dependencies between a component and
       its clients.
    </p>
-   <p>
+   
+<p>
       For example, suppose that the application Foo depends
       (only) upon features of the commons-superwidget component
       that are part of the external interface in release 2.3.0.
@@ -821,7 +916,8 @@
       certainty that Foo will work with any 2.x release of
       superwidget (x &gt;= 3).
    </p>
-   <p>
+   
+<p>
       Similarly, suppose the application Bar depends upon
       features of superwidget that were part of the internal
       interface of release 2.3.0.  Then the maintainers of Bar
@@ -830,22 +926,24 @@
       (or 3.0) is released will Bar's developers have to
       re-evaluate.
    </p>
-  </div>
+  
+</div>
 </p>
 </div>
 <div class="section">
 <div class="section-header">
-<a name="End Notes">
-<strong>End Notes</strong>
-</a>
+<a name="End%20Notes"><strong>End Notes</strong></a>
 </div>
 <p>
 <div class="section-body">
-   <dl>
-    <dt>
+   
+<dl>
+    
+<dt>
 <a name="note1">Note 1</a>
 </dt>
-    <dd>
+    
+<dd>
      We say "nearly" here since there are rare
      or unusual circumstances in which changes that are usually
      "safe" may cause problems for a small number of users.
@@ -855,16 +953,18 @@
      class and already added a method with the same signature in
      their subclass.
     </dd>
-   </dl>
-  </div>
+   
+</dl>
+  
+</div>
 </p>
 </div>
 </td>
-<!--RIGHT SIDE NAVIGATION-->
-<td nowrap="true" valign="top" class="right-navbar">
+<!--RIGHT SIDE NAVIGATION--><td nowrap="true" valign="top" class="right-navbar">
 <navbar name="rhs">
 
-    <p>
+    
+<p>
 <strong>About Jakarta</strong>
 </p>
 <ul>
@@ -887,7 +987,8 @@
 <a href="http://jakarta.apache.org/site/java_at_apache.html">Java@Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Reference</strong>
 </p>
 <ul>
@@ -919,17 +1020,23 @@
 <a href="http://www.apache.org/foundation/thanks.html">Acknowledgements</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Search Jakarta</strong>
 </p>
 <div class="searchbox">
-        <form action="http://www.google.com/search" method="get">
-          <input value="jakarta.apache.org" name="sitesearch" type="hidden" />
-          <input size="10" name="q" id="query" type="text" />
-          <input name="Search" value="Search" type="submit" />
-        </form>
-      </div>
-    <p>
+        
+<form action="http://www.google.com/search" method="get">
+          
+<input value="jakarta.apache.org" name="sitesearch" type="hidden">
+          <input size="10" name="q" id="query" type="text">
+          <input name="Search" value="Search" type="submit">
+        
+</form>
+      
+</div>
+    
+<p>
 <strong>Unaffiliated Links</strong>
 </p>
 <ul>
@@ -946,7 +1053,8 @@
 <a href="http://www.planetapache.org/">Planet Apache</a>
 </li>
 </ul>
-    <p>
+    
+<p>
 <strong>Unaffiliated Translations</strong>
 </p>
 <ul>
@@ -960,20 +1068,21 @@
 <a href="http://jakarta.jp/">Jakarta.JP (Japanese)</a>
 </li>
 </ul>
+
 </navbar>
 </td>
 </tr>
 <!--FOOTER SEPARATOR-->
 <tr>
 <td colspan="3">
-<hr size="1" noshade="" />
+<hr size="1" noshade="">
 </td>
 </tr>
 <tr>
 <td colspan="3">
 <div class="page-footer">
 <em>
-        Copyright © 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
+        Copyright &copy; 1999-2005, The Apache Software Foundation. <a href="http://jakarta.apache.org/site/legal.html">Legal information</a>.
         </em>
 </div>
 </td>



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


Mime
View raw message