incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r469294 - in /incubator/public/trunk: site-author/guides/releasemanagement.xml site-publish/guides/releasemanagement.html
Date Mon, 30 Oct 2006 22:14:58 GMT
Author: rdonkin
Date: Mon Oct 30 14:14:57 2006
New Revision: 469294

URL: http://svn.apache.org/viewvc?view=rev&rev=469294
Log:
Kicked off a couple of new sections.

Modified:
    incubator/public/trunk/site-author/guides/releasemanagement.xml
    incubator/public/trunk/site-publish/guides/releasemanagement.html

Modified: incubator/public/trunk/site-author/guides/releasemanagement.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/releasemanagement.xml?view=diff&rev=469294&r1=469293&r2=469294
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml Mon Oct 30 14:14:57 2006
@@ -238,6 +238,25 @@
     	</p>
     </section>
     <section id='best-practice'><title>Best Practice</title>
+    	<section id='best-practice-preparation'><title>Preparation</title>
+			<ul>
+				<li>Analyse <a href='#best-practice-prepare-documentation'>bugs</a></li>
+				<li>Check <a href='#best-practice-prepare-documentation'>documentation</a></li>
+			</ul>
+    	</section>
+    	<section id='best-practice-bugs'><title>Bugs</title>
+    		<p>
+The list of open bugs needs to be analysed. TODO: expand
+    		</p>
+    	</section>
+    	<section id='best-practice-prepare-documentation'><title>Preparing Documentation</title>
+    		<p>
+Any documentation that the release contains should be proof-read and spell checked.
+This is obviously something that needs to happen after the content is finalised.
+So typically, the release manager needs to coordinate the documentation effort.
+A release is a good time to concentrate energy on documentation.
+    		</p>
+    	</section>
         <section id='best-practice-jars'><title>Jars</title>
             <ul>
                 <li><code>META-INF</code>

Modified: incubator/public/trunk/site-publish/guides/releasemanagement.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasemanagement.html?view=diff&rev=469294&r1=469293&r2=469294
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html Mon Oct 30 14:14:57
2006
@@ -344,6 +344,34 @@
 </h2>
 <div class="section-content">
 <h3>
+   <a name="best-practice-preparation">Preparation</a>
+</h3>
+<div class="section-content">
+<ul>
+				<li>Analyse <a href="#best-practice-prepare-documentation">bugs</a></li>
+				<li>Check <a href="#best-practice-prepare-documentation">documentation</a></li>
+			</ul>
+</div>
+<h3>
+   <a name="best-practice-bugs">Bugs</a>
+</h3>
+<div class="section-content">
+<p>
+The list of open bugs needs to be analysed. TODO: expand
+    		</p>
+</div>
+<h3>
+   <a name="best-practice-prepare-documentation">Preparing Documentation</a>
+</h3>
+<div class="section-content">
+<p>
+Any documentation that the release contains should be proof-read and spell checked.
+This is obviously something that needs to happen after the content is finalised.
+So typically, the release manager needs to coordinate the documentation effort.
+A release is a good time to concentrate energy on documentation.
+    		</p>
+</div>
+<h3>
    <a name="best-practice-jars">Jars</a>
 </h3>
 <div class="section-content">



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


Mime
View raw message