incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r851945 - in /websites/staging/incubator/trunk/content: ./ guides/releasemanagement.html report-next-month.html sitemap.html
Date Mon, 25 Feb 2013 22:44:18 GMT
Author: buildbot
Date: Mon Feb 25 22:44:18 2013
New Revision: 851945

Staging update by buildbot for incubator

    websites/staging/incubator/trunk/content/   (props changed)

Propchange: websites/staging/incubator/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 25 22:44:18 2013
@@ -1 +1 @@

Modified: websites/staging/incubator/trunk/content/guides/releasemanagement.html
--- websites/staging/incubator/trunk/content/guides/releasemanagement.html (original)
+++ websites/staging/incubator/trunk/content/guides/releasemanagement.html Mon Feb 25 22:44:18
@@ -342,10 +342,6 @@ Binary Package
 Release Documentation
-<li><a href='#best-practice-status'>
-STATUS document
- </a>
 <li><a href='#best-practice-license'>
@@ -1218,7 +1214,6 @@ available on auxiliary pages.
                     <li>Check incubator requirements
                     		<li>Check <a href="#notes-disclaimer">disclaimer</a>
is distributed TODO: link</li>
-                    		<li>Check <a href="#best-practice-status">status document</a></li>
@@ -1477,11 +1472,6 @@ including source packages.
 So the master documents should be checked into the base subversion directory.
-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>
 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. 
@@ -1516,14 +1506,6 @@ with each release as adoption grows.
  and in ANNOUNCEMENTSs (TODO add links to this in announcements section)
-<h3 id='best-practice-status'>STATUS document</h3>
-<div class="section-content">
-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
-before releasing. The legal STATUS of the code base should be clean before it is released.
-        	</p>
 <h3 id='best-practice-license'>LICENSE and NOTICE</h3>
 <div class="section-content">

Modified: websites/staging/incubator/trunk/content/report-next-month.html
--- websites/staging/incubator/trunk/content/report-next-month.html (original)
+++ websites/staging/incubator/trunk/content/report-next-month.html Mon Feb 25 22:44:18 2013
@@ -67,7 +67,7 @@
 <a href="">Apache Incubator</a> Podlings needing to
prepare report for March</h1>
 <div style="text-align:right;">
-<i>Generated on 2013-02-25T21:50:42Z</i>
+<i>Generated on 2013-02-25T22:44:07Z</i>

Modified: websites/staging/incubator/trunk/content/sitemap.html
--- websites/staging/incubator/trunk/content/sitemap.html (original)
+++ websites/staging/incubator/trunk/content/sitemap.html Mon Feb 25 22:44:18 2013
@@ -1281,9 +1281,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#best-practice-documentation">Release Documentation</a>
-<a href="guides/releasemanagement.html#best-practice-status">STATUS document</a>
 <a href="guides/releasemanagement.html#best-practice-license">LICENSE and NOTICE</a>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message