incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r437728 - in /incubator/public/trunk: site-author/guides/releasemanagement.xml site-publish/guides/releasemanagement.html
Date Mon, 28 Aug 2006 15:29:29 GMT
Author: rdonkin
Date: Mon Aug 28 08:29:29 2006
New Revision: 437728

URL: http://svn.apache.org/viewvc?rev=437728&view=rev
Log:
Added 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?rev=437728&r1=437727&r2=437728&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml Mon Aug 28 08:29:29 2006
@@ -100,6 +100,15 @@
         TODO: legal consequences
             </li>
         </ul>
+        <p>
+A podling should have a release guide. A good starting point (once this document has been
read)
+is release guides for existing projects:
+        </p>
+        <ul>
+        	<li><a href='http://httpd.apache.org/dev/release.html'>HTTPD</a></li>
+        	<li><a href='http://jakarta.apache.org/commons'>Jakarta Commons</a></li>
+        	<li><a href='http://struts.apache.org/releases.html'>Struts</a></li>
+        </ul>
     </section>
     <section id='check-list'><title>Check List</title>
         <p>
@@ -251,7 +260,16 @@
     <section id='notes'><title>Notes</title>
         <section id='distributing-jars'><title>Distributing Jars</title>
             <p>
-            TODO
+            TODO: link to infrastructure
+            </p>
+            <p>
+Jars are just another form of binary distribution. If they are likely to be distributed
+(for example, through the Apache Repository) then they must adhere to the same policy
+as other binary distributions. In particular, LICENSE and NOTICE files must be distributed.
+            </p>
+            <p>
+It is convenient to include these with the META-INF directory. This can be done easily either

+either with Ant or Maven. TODO: move examples here from jakarta commons releases.
             </p>
         </section>
         <section id='jar-manifest'><title>Jar MANIFEST</title>
@@ -259,6 +277,8 @@
 TODO
 Lots of projects get this wrong and (by default) most tools produce substandard manifests.
 Offer some guidance on values
+TODO: Add how to create a specification complient MANIFEST 
+http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
             </p>
         </section>
         <section id='release-notes'><title>Release Notes</title>

Modified: incubator/public/trunk/site-publish/guides/releasemanagement.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasemanagement.html?rev=437728&r1=437727&r2=437728&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html Mon Aug 28 08:29:29
2006
@@ -178,6 +178,15 @@
         TODO: legal consequences
             </li>
         </ul>
+<p>
+A podling should have a release guide. A good starting point (once this document has been
read)
+is release guides for existing projects:
+        </p>
+<ul>
+        	<li><a href="http://httpd.apache.org/dev/release.html">HTTPD</a></li>
+        	<li><a href="http://jakarta.apache.org/commons">Jakarta Commons</a></li>
+        	<li><a href="http://struts.apache.org/releases.html">Struts</a></li>
+        </ul>
 </div>
            <h2><img src="/images/redarrow.gif" />
    <a name="check-list">Check List</a>
@@ -374,7 +383,16 @@
 </h3>
 <div class="section-content">
 <p>
-            TODO
+            TODO: link to infrastructure
+            </p>
+<p>
+Jars are just another form of binary distribution. If they are likely to be distributed
+(for example, through the Apache Repository) then they must adhere to the same policy
+as other binary distributions. In particular, LICENSE and NOTICE files must be distributed.
+            </p>
+<p>
+It is convenient to include these with the META-INF directory. This can be done easily either

+either with Ant or Maven. TODO: move examples here from jakarta commons releases.
             </p>
 </div>
 <h3>
@@ -385,6 +403,8 @@
 TODO
 Lots of projects get this wrong and (by default) most tools produce substandard manifests.
 Offer some guidance on values
+TODO: Add how to create a specification complient MANIFEST 
+http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
             </p>
 </div>
 <h3>



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


Mime
View raw message