incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mar...@apache.org
Subject svn commit: r1449949 - /incubator/public/trunk/content/guides/releasemanagement.xml
Date Mon, 25 Feb 2013 22:44:03 GMT
Author: marvin
Date: Mon Feb 25 22:44:03 2013
New Revision: 1449949

URL: http://svn.apache.org/r1449949
Log:
Remove mention of the STATUS document.

The STATUS document, a "to-do" list maintained at the root of the source
tree (*not* the podling incubation status file at
incubator.apache.org/projects/foo.html), is a convention adopted by some
Apache projects, such as Apache HTTPD.  However, podlings may use
whatever means they choose to track their progress, and description of
how to use a STATUS document belongs elsewhere.

Modified:
    incubator/public/trunk/content/guides/releasemanagement.xml

Modified: incubator/public/trunk/content/guides/releasemanagement.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/releasemanagement.xml?rev=1449949&r1=1449948&r2=1449949&view=diff
==============================================================================
--- incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] Mon Feb 25 22:44:03
2013
@@ -635,7 +635,6 @@ TODO: maybe be better in a time line
                     <li>Check incubator requirements
                     	<ul>
                     		<li>Check <a href='#notes-disclaimer'>disclaimer</a>
is distributed TODO: link</li>
-                    		<li>Check <a href='#best-practice-status'>status document</a></li>
                     	</ul>
                     </li>
                 </ul>
@@ -878,11 +877,6 @@ including source packages.
 So the master documents should be checked into the base subversion directory.
         	</p>
         	<p>
-TODO: rewrite to be topic centric.
-* project status. DISCLAIMER or STATUS 
-Incubating projects should ensure that either contain the STATUS document describing. TODO:
check this
-        	</p>
-        	<p>
 Collecting all this information may seem a little daunting especially for a starting project.
 Not at all agile. One approach may be to ask developers to update documentation
 as they make changes. 
@@ -917,13 +911,6 @@ with each release as adoption grows.
  and in ANNOUNCEMENTSs (TODO add links to this in announcements section)
         	</p>
         </section>
-        <section id='best-practice-status'><title>STATUS document</title>
-        	<p>
-TODO: check this TODO: the STATUS document should be checked to ensure that it is up to date
-before release. Incubator releases should do a <a href='#best-practice-audit'>legal
audit</a> 
-before releasing. The legal STATUS of the code base should be clean before it is released.
-        	</p>
-        </section>
         <section id='best-practice-license'><title>LICENSE and NOTICE</title>
         	<p>
 Apache projects may distribute artifacts and documents as part of a release



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


Mime
View raw message