incubator-cvs mailing list archives

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

URL: http://svn.apache.org/viewvc?view=rev&rev=448614
Log:
Added more rough 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=448614&r1=448613&r2=448614
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml Thu Sep 21 10:47:13 2006
@@ -457,6 +457,18 @@
 TODO: Add how to create a specification complient MANIFEST 
 http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
             </p>
+            <p>
+Maven 1 produces a minimal MANIFEST. This should be augemented with the 
+recommended by adding appropriate 
+<a href='http://maven.apache.org/maven-1.x/plugins/jar/properties.html'>properties</a>
+to the <code>project.properties</code> file.
+            </p>
+            <p>
+Maven 2 produces a much better manifest provided that the POM is reasonably full.
+It does not (by default) include some recommended. It is recommended that POM should be
+<a href='http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html'>customized</a>
+so that it includes the missing recommendation.
+            </p>
         </section>
         <section id='best-practice-release-candidate'><title>Release Candidates</title>
               <p>
@@ -708,6 +720,36 @@
         	</p>
         	<p>
 TODO: move VOTE netiquette into either ppmc or lists and link from here
+TODO: this has turned into best practice.
+        	</p>
+        </section>
+        <section id='notes-revote'><title>On Managing VOTE Threads</title>
+        	<p>
+        	TODO: consider whether this would be better moved elsewhere
+        	</p>
+        	<p>
+VOTEs on low volume mailing lists with small numbers of interested parties 
+usually require no management. VOTE threads on high volume mailing lists 
+or mailing lists with large numbers of active contributors require netiquette
+and active management to avoid confusion. It is not uncommon for those
+unfamiliar with these environments to find difficulties.
+        	</p>
+        	<p>
+Long VOTE threads are hard to tally. Each opinion needs to be noted and ackowledged.
+This allows people to check their votes and easily correct mistakes in the count.
+        	</p>
+        	<p>
+ It is vital in a long VOTE to ensure that debate is restricted on the VOTE thread.
+ If it looks likely that there is a risk that a VOTE will turn into a debate,
+ it is wise to allow people to discuss the issues first.
+ It is important that off topic or divergent posts are moved to separate threads with
+ other subjects. 
+        	</p>
+        	<p>
+ It is usually cleaner to abandone a VOTE thread that goes estray or when the proposal
+ needs to be altered - for example, then issues are found in a release candidate. 
+ Start a new VOTE thread with the revised proposal (in the case of the example, a new
+ release candidate).
         	</p>
         </section>
         <section id='notes-release-candidate-java'><title>On Java Release Candidates</title>
@@ -725,6 +767,31 @@
 uniquely named. Uncertainty about exact jar versions has caused nasty dependency
 issues in the past.
 			</p>
+        </section>
+        <section id='notes-on-gnu-tar'><title>GNU Tar Known Incompatibilities</title>
+        	<p>
+Typically, applications used to create <code>tar.gz</code> files are based on
+GNU tar. Unfortunately, the tar which ships with some versions of Solaris and some
+(older) versions of MacOSX is not always compatible with the output of GNU tar.
+        	TODO: check information and expand
+        	</p>
+        </section>
+        <section id='notes-on-source-only-releases'><title>On Source Only Releases</title>
+        	<p>
+A source only release contains only the source distribution. Though users often prefer
+binary distributions, source only releases can be useful early in the life of a project.

+They require much less ceremony and encourage developers to get involved by finding 
+and fixing bugs. Occasionally, projects whose primary user base typically obtains 
+the software via a downstream repackage may prefer to release source only.
+        	</p>
+        </section>
+        <section id='notes-on-binary-only-releases'><title>On Binary Only Releases</title>
+        	<p>
+Releases containing only binary distributions are strongly frowned upon. Open source 
+development is characterised by the accessibility of the source. Binary only distributions
+discourage developers from interacting with the source. Every successful Apache
+project needs to recruit new developers to carry the project forward.
+        	</p>
         </section>
     </section>
     <section id='glossary'><title>Glossary</title>

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=448614&r1=448613&r2=448614
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html Thu Sep 21 10:47:13
2006
@@ -615,6 +615,18 @@
 TODO: Add how to create a specification complient MANIFEST 
 http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
             </p>
+<p>
+Maven 1 produces a minimal MANIFEST. This should be augemented with the 
+recommended by adding appropriate 
+<a href="http://maven.apache.org/maven-1.x/plugins/jar/properties.html">properties</a>
+to the <code>project.properties</code> file.
+            </p>
+<p>
+Maven 2 produces a much better manifest provided that the POM is reasonably full.
+It does not (by default) include some recommended. It is recommended that POM should be
+<a href="http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html">customized</a>
+so that it includes the missing recommendation.
+            </p>
 </div>
 <h3>
    <a name="best-practice-release-candidate">Release Candidates</a>
@@ -901,6 +913,39 @@
         	</p>
 <p>
 TODO: move VOTE netiquette into either ppmc or lists and link from here
+TODO: this has turned into best practice.
+        	</p>
+</div>
+<h3>
+   <a name="notes-revote">On Managing VOTE Threads</a>
+</h3>
+<div class="section-content">
+<p>
+        	TODO: consider whether this would be better moved elsewhere
+        	</p>
+<p>
+VOTEs on low volume mailing lists with small numbers of interested parties 
+usually require no management. VOTE threads on high volume mailing lists 
+or mailing lists with large numbers of active contributors require netiquette
+and active management to avoid confusion. It is not uncommon for those
+unfamiliar with these environments to find difficulties.
+        	</p>
+<p>
+Long VOTE threads are hard to tally. Each opinion needs to be noted and ackowledged.
+This allows people to check their votes and easily correct mistakes in the count.
+        	</p>
+<p>
+ It is vital in a long VOTE to ensure that debate is restricted on the VOTE thread.
+ If it looks likely that there is a risk that a VOTE will turn into a debate,
+ it is wise to allow people to discuss the issues first.
+ It is important that off topic or divergent posts are moved to separate threads with
+ other subjects. 
+        	</p>
+<p>
+ It is usually cleaner to abandone a VOTE thread that goes estray or when the proposal
+ needs to be altered - for example, then issues are found in a release candidate. 
+ Start a new VOTE thread with the revised proposal (in the case of the example, a new
+ release candidate).
         	</p>
 </div>
 <h3>
@@ -921,6 +966,40 @@
 uniquely named. Uncertainty about exact jar versions has caused nasty dependency
 issues in the past.
 			</p>
+</div>
+<h3>
+   <a name="notes-on-gnu-tar">GNU Tar Known Incompatibilities</a>
+</h3>
+<div class="section-content">
+<p>
+Typically, applications used to create <code>tar.gz</code> files are based on
+GNU tar. Unfortunately, the tar which ships with some versions of Solaris and some
+(older) versions of MacOSX is not always compatible with the output of GNU tar.
+        	TODO: check information and expand
+        	</p>
+</div>
+<h3>
+   <a name="notes-on-source-only-releases">On Source Only Releases</a>
+</h3>
+<div class="section-content">
+<p>
+A source only release contains only the source distribution. Though users often prefer
+binary distributions, source only releases can be useful early in the life of a project.

+They require much less ceremony and encourage developers to get involved by finding 
+and fixing bugs. Occasionally, projects whose primary user base typically obtains 
+the software via a downstream repackage may prefer to release source only.
+        	</p>
+</div>
+<h3>
+   <a name="notes-on-binary-only-releases">On Binary Only Releases</a>
+</h3>
+<div class="section-content">
+<p>
+Releases containing only binary distributions are strongly frowned upon. Open source 
+development is characterised by the accessibility of the source. Binary only distributions
+discourage developers from interacting with the source. Every successful Apache
+project needs to recruit new developers to carry the project forward.
+        	</p>
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />



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


Mime
View raw message