commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bay...@apache.org
Subject svn commit: r928582 - /commons/proper/commons-site/trunk/src/site/xdoc/releases/index.xml
Date Mon, 29 Mar 2010 03:29:28 GMT
Author: bayard
Date: Mon Mar 29 03:29:26 2010
New Revision: 928582

URL: http://svn.apache.org/viewvc?rev=928582&view=rev
Log:
Cutting some of the text. Feedback section unnecessary. Keeping the focus on the novice reader
not legal bureaucracy (components who differ must document statement)

Modified:
    commons/proper/commons-site/trunk/src/site/xdoc/releases/index.xml

Modified: commons/proper/commons-site/trunk/src/site/xdoc/releases/index.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-site/trunk/src/site/xdoc/releases/index.xml?rev=928582&r1=928581&r2=928582&view=diff
==============================================================================
--- commons/proper/commons-site/trunk/src/site/xdoc/releases/index.xml (original)
+++ commons/proper/commons-site/trunk/src/site/xdoc/releases/index.xml Mon Mar 29 03:29:26
2010
@@ -28,15 +28,13 @@
     <subsection name='Introduction'>
         <p>
         The <em>Apache Commons</em> project differs from many other Apache projects
because 
-        it is comprised of multiple, independently released components. Therefore, the release
procedure
-        for an individual component needs to be documented so that component authors follow
consistent
-        practices.
+        it is comprised of multiple, independently released components. The common release
procedure
+        for an individual component is documented here so that contributors can easily move
from 
+        component to component. 
         </p>
         <p>
-        Individual components (such as Collections) might vary from these practices 
-        but these steps should prove sufficient for the majority
-        of cases. Any components which deviate substantially from this procedure should document
these 
-        deviations.
+        Individual components may vary from these practices, but these steps should prove
sufficient for the majority
+        of cases. 
         </p>
     </subsection>
     <subsection name='Documentation'>
@@ -50,14 +48,5 @@
         </p>
     </subsection>
   </section>
-  <section name='Feedback'>
-        <p>
-        Feedback - yes please! 
-        </p>
-        <p>
-        Comments, critiques and error reports -
-        post them any and all to the dev mailing list at commons.apache.org. Please prefix
with [doc].
-        </p>
-  </section>
  </body>
 </document>



Mime
View raw message