incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r485159 - in /incubator/public/trunk: site-author/guides/releasemanagement.xml site-publish/guides/releasemanagement.html
Date Sun, 10 Dec 2006 11:48:57 GMT
Author: rdonkin
Date: Sun Dec 10 03:48:56 2006
New Revision: 485159

URL: http://svn.apache.org/viewvc?view=rev&rev=485159
Log:
More content

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=485159&r1=485158&r2=485159
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml Sun Dec 10 03:48:56 2006
@@ -71,6 +71,11 @@
 are encouraged.
     </p>
     </section>
+    <section name='references'><title>References</title>
+        <p>
+        TODO: links to project management books.
+        </p>
+    </section>
     </section>
     <section id='guidelines'><title>Guidelines</title>
     	<p>
@@ -651,6 +656,36 @@
 <code>apache.org</code> address.
         	</p>
         </section>
+        <section id='best-practice-incubator-release-vote'><title>Incubator Release
Vote</title>
+            <p>
+All releases by podlings must be approved by the TODO: link IPMC. The conventional process
+is for the podling to follow the usual Apache process (including TODO: link release vote)
+and then call for a IPMC VOTE on the TODO: link general incubator list.
+            </p>
+            <p>
+The release manager should post the call for the VOTE. 
+            </p>
+            <ul>
+                <li>Links to the release artifacts</li>
+                <li>Links to the PPMC release vote thread</li>
+                <li>Link to the tag from which the release is cut</li>
+            </ul>
+        </section>
+        <section id='best-practice-mailing-lists'><title></title>
+            <p>
+Release managers should subscribe to a number of Apache-wide mailing lists.
+Decisions are taken on these mailing lists and issues resolved.
+Documentation is updated later (if at all). It's important that release
+managers ensure that they keep up to date.
+            </p>
+            <ul>
+                <li>TODO: link General infrastructure list</li>
+                <li>TODO: link Legal discuss list</li>
+            </ul>
+            <p>
+Release managers for incubating podlings should also subscribe to the TODO: link general
list.
+            </p>
+        </section>
         <section id='best-practices-release-candidates'><title>Release Candidates</title>
         	<p>
 A release candidate is a artifact upon which a vote is held for a release.
@@ -821,12 +856,23 @@
         	</p>
         </section>
         <section id='release-notes'><title>Release Notes</title>
+            <p>
+TODO: rewrite this is section distinguishing between the content and the presentation.
+content may (and probably should) be replicated in many different places.
+The content presented in the RELEASE_NOTES needs to be plain text etc
+            </p>
         	<p>
 Release notes are a vital tool for communication between an open source project 
 and it's users. They are often the first documentation a user will read. First
 impressions matter. Their content will often serve as the basis for TODO: link
 announcements and other TODO: link grassroots pubicity.
         	</p>
+            <p>
+The content may be replicated in many places. Use the content as news on the
+project website and as the basis for the download page. Use the content for 
+posting to TODO: link  grassroots media. Use the content for postings to 
+announcement lists.
+            </p>
             <p>
 The release notes should be in a common and easily read format (plain text is best).
 The release notes should easily located and so should be positioned in the base directory.

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=485159&r1=485158&r2=485159
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html Sun Dec 10 03:48:56
2006
@@ -152,6 +152,14 @@
 are encouraged.
     </p>
 </div>
+<h3>
+   References
+</h3>
+<div class="section-content">
+<p>
+        TODO: links to project management books.
+        </p>
+</div>
 </div>
            <h2><img src="/images/redarrow.gif" />
    <a name="guidelines">Guidelines</a>
@@ -833,6 +841,42 @@
         	</p>
 </div>
 <h3>
+   <a name="best-practice-incubator-release-vote">Incubator Release Vote</a>
+</h3>
+<div class="section-content">
+<p>
+All releases by podlings must be approved by the TODO: link IPMC. The conventional process
+is for the podling to follow the usual Apache process (including TODO: link release vote)
+and then call for a IPMC VOTE on the TODO: link general incubator list.
+            </p>
+<p>
+The release manager should post the call for the VOTE. 
+            </p>
+<ul>
+                <li>Links to the release artifacts</li>
+                <li>Links to the PPMC release vote thread</li>
+                <li>Link to the tag from which the release is cut</li>
+            </ul>
+</div>
+<h3>
+   <a name="best-practice-mailing-lists"></a>
+</h3>
+<div class="section-content">
+<p>
+Release managers should subscribe to a number of Apache-wide mailing lists.
+Decisions are taken on these mailing lists and issues resolved.
+Documentation is updated later (if at all). It's important that release
+managers ensure that they keep up to date.
+            </p>
+<ul>
+                <li>TODO: link General infrastructure list</li>
+                <li>TODO: link Legal discuss list</li>
+            </ul>
+<p>
+Release managers for incubating podlings should also subscribe to the TODO: link general
list.
+            </p>
+</div>
+<h3>
    <a name="best-practices-release-candidates">Release Candidates</a>
 </h3>
 <div class="section-content">
@@ -1034,11 +1078,22 @@
 </h3>
 <div class="section-content">
 <p>
+TODO: rewrite this is section distinguishing between the content and the presentation.
+content may (and probably should) be replicated in many different places.
+The content presented in the RELEASE_NOTES needs to be plain text etc
+            </p>
+<p>
 Release notes are a vital tool for communication between an open source project 
 and it's users. They are often the first documentation a user will read. First
 impressions matter. Their content will often serve as the basis for TODO: link
 announcements and other TODO: link grassroots pubicity.
         	</p>
+<p>
+The content may be replicated in many places. Use the content as news on the
+project website and as the basis for the download page. Use the content for 
+posting to TODO: link  grassroots media. Use the content for postings to 
+announcement lists.
+            </p>
 <p>
 The release notes should be in a common and easily read format (plain text is best).
 The release notes should easily located and so should be positioned in the base directory.



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


Mime
View raw message