incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r443111 - in /incubator/public/trunk: site-author/guides/releasemanagement.xml site-publish/guides/releasemanagement.html
Date Wed, 13 Sep 2006 20:23:21 GMT
Author: rdonkin
Date: Wed Sep 13 13:23:21 2006
New Revision: 443111

URL: http://svn.apache.org/viewvc?view=rev&rev=443111
Log:
Adding a few more topics that should be filled later.

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=443111&r1=443110&r2=443111
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml Wed Sep 13 13:23:21 2006
@@ -73,6 +73,10 @@
     </section>
     </section>
     <section id='guidelines'><title>Guidelines</title>
+    	<p>
+  TODO: may need to think about this title. The idea is to try to clearly separate guidelines
+  about release processes and procedures from rules and guidelines.
+    	</p>
     	<section id='process'><title>Release Process</title>
     		<p>
 The minimal formal requirements for an official ASF release are (contrary to rumor) minimal.
@@ -195,7 +199,8 @@
     </section>
     <section id='rules'><title>Rules</title>
         <p>
-        TODO release votes by pmc, legal rules, infrastructure rules. Use links so information
is maintained 
+        TODO release votes by pmc, legal rules (licenses of distributed dependencies, source
licenses, LICENSE, NOTICE), 
+        infrastructure rules(signing). Use links so information is maintained 
         in only one place.
         </p>
         <section id='naming'>Naming<title></title>
@@ -204,6 +209,18 @@
             </p>
         </section>
     </section>
+    <section id='release-guidelines'><title>Release Guidelines</title>
+    	<p>
+In addition to policy, the infrastructure, public relations and legal teams also
+document <a href='#glossary-guidelines'>guidelines</a> for projects.
+There are almost certainly good reasons why a project should follow
+these guidelines but they have not been blessed as policy.
+    	</p>
+    	<p>
+Guidelines change much more frequently than policy. Release managers should follow the appropriate
+lists (TODO: create list of useful mailing lists).
+    	</p>
+    </section>
     <section id='best-practice'><title>Best Practice</title>
         <section id='best-practice-jars'><title>Jars</title>
             <ul>
@@ -671,6 +688,13 @@
 The actual execution of the release. Typically consists of building the distribtions
 from the repository tag.
 TODO: link to infra
+        	</p>
+        </section>
+        <section id='glossary-guidelines'><title>Guidelines</title>
+        	<p>
+Guidelines are documented recommendations which have not yet been blessed as policy.
+There are usually good reasons why project should follow the guidelines given
+even if these may be initially obvious.
         	</p>
         </section>
     </section>

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=443111&r1=443110&r2=443111
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html Wed Sep 13 13:23:21
2006
@@ -152,6 +152,10 @@
    <a name="guidelines">Guidelines</a>
 </h2>
 <div class="section-content">
+<p>
+  TODO: may need to think about this title. The idea is to try to clearly separate guidelines
+  about release processes and procedures from rules and guidelines.
+    	</p>
 <h3>
    <a name="process">Release Process</a>
 </h3>
@@ -286,7 +290,8 @@
 </h2>
 <div class="section-content">
 <p>
-        TODO release votes by pmc, legal rules, infrastructure rules. Use links so information
is maintained 
+        TODO release votes by pmc, legal rules (licenses of distributed dependencies, source
licenses, LICENSE, NOTICE), 
+        infrastructure rules(signing). Use links so information is maintained 
         in only one place.
         </p>
 <h3>
@@ -299,6 +304,21 @@
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />
+   <a name="release-guidelines">Release Guidelines</a>
+</h2>
+<div class="section-content">
+<p>
+In addition to policy, the infrastructure, public relations and legal teams also
+document <a href="#glossary-guidelines">guidelines</a> for projects.
+There are almost certainly good reasons why a project should follow
+these guidelines but they have not been blessed as policy.
+    	</p>
+<p>
+Guidelines change much more frequently than policy. Release managers should follow the appropriate
+lists (TODO: create list of useful mailing lists).
+    	</p>
+</div>
+           <h2><img src="/images/redarrow.gif" />
    <a name="best-practice">Best Practice</a>
 </h2>
 <div class="section-content">
@@ -885,6 +905,16 @@
 The actual execution of the release. Typically consists of building the distribtions
 from the repository tag.
 TODO: link to infra
+        	</p>
+</div>
+<h3>
+   <a name="glossary-guidelines">Guidelines</a>
+</h3>
+<div class="section-content">
+<p>
+Guidelines are documented recommendations which have not yet been blessed as policy.
+There are usually good reasons why project should follow the guidelines given
+even if these may be initially obvious.
         	</p>
 </div>
 </div>



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


Mime
View raw message