incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r828105 - in /websites/staging/incubator/trunk/content: ./ guides/releasemanagement.html report-next-month.html sitemap.html
Date Mon, 06 Aug 2012 03:33:01 GMT
Author: buildbot
Date: Mon Aug  6 03:33:01 2012
New Revision: 828105

Log:
Staging update by buildbot for incubator

Modified:
    websites/staging/incubator/trunk/content/   (props changed)
    websites/staging/incubator/trunk/content/guides/releasemanagement.html
    websites/staging/incubator/trunk/content/report-next-month.html
    websites/staging/incubator/trunk/content/sitemap.html

Propchange: websites/staging/incubator/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Aug  6 03:33:01 2012
@@ -1 +1 @@
-1369717
+1369718

Modified: websites/staging/incubator/trunk/content/guides/releasemanagement.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/releasemanagement.html (original)
+++ websites/staging/incubator/trunk/content/guides/releasemanagement.html Mon Aug  6 03:33:01
2012
@@ -265,10 +265,6 @@ Signatures
 Dealing With A Defect
  </a>
 </li>
-<li><a href='#distributing-eclipse'>
-Eclipse Update Site
- </a>
-</li>
 </ul>
 </li>
 </ul>
@@ -315,10 +311,6 @@ Bugs
 Preparing Documentation
  </a>
 </li>
-<li><a href='#best-practice-jars'>
-Jars
- </a>
-</li>
 <li><a href='#best-practice-naming'>
 Artifact Naming
  </a>
@@ -411,10 +403,6 @@ Release Candidates
 Signatures
  </a>
 </li>
-<li><a href='#best-practice-maven'>
-Maven
- </a>
-</li>
 </ul>
 </li>
 <li><a href='#notes'>
@@ -429,14 +417,6 @@ License Issues
 The Incubator Disclaimer
  </a>
 </li>
-<li><a href='#distributing-jars'>
-Distributing Jars
- </a>
-</li>
-<li><a href='#jar-manifest'>
-Jar MANIFEST
- </a>
-</li>
 <li><a href='#best-practice-release-candidate'>
 Release Candidates
  </a>
@@ -457,10 +437,6 @@ Unique Artifact Names
 Release Notes
  </a>
 </li>
-<li><a href='#note-compatibility-checkers'>
-Compatibility Checkers
- </a>
-</li>
 <li><a href='#notes-change-log'>
 Change Logs
  </a>
@@ -477,10 +453,6 @@ On Multiple Products
 On Template Sources
  </a>
 </li>
-<li><a href='#notes-on-java-version'>
-On Java Versions
- </a>
-</li>
 <li><a href='#notes-on-export-regulations'>
 On Export Regulations
  </a>
@@ -497,10 +469,6 @@ On Line Endings
 On Press Releases
  </a>
 </li>
-<li><a href='#notes-on-signing-jars'>
-On Signing Jars
- </a>
-</li>
 <li><a href='#notes-license-headers'>
 On License Headers
  </a>
@@ -512,12 +480,6 @@ Code Provenance
 <li><a href='#note-standards'>
 Implementations Of Standards
  </a>
- <ul>
-<li><a href='#notes-jsr'>
-JSRs
- </a>
-</li>
-</ul>
 </li>
 <li><a href='#note-license-and-notice'>
 Understanding Content For NOTICE and LICENSE
@@ -537,10 +499,6 @@ VOTEs
 On Managing VOTE Threads
  </a>
 </li>
-<li><a href='#notes-release-candidate-java'>
-On Java Release Candidates
- </a>
-</li>
 <li><a href='#notes-on-gnu-tar'>
 GNU Tar Known Incompatibilities
  </a>
@@ -583,10 +541,6 @@ NOTICE file
 Ceremony
  </a>
 </li>
-<li><a href='#glossary-manifest'>
-Jar MANIFEST
- </a>
-</li>
 <li><a href='#glossary-license-header'>
 License Header
  </a>
@@ -1218,24 +1172,6 @@ are encouraged.
           <li>Adding a suitable notice to the download page</li>
           </ol>
 </div>
-<h4 id='distributing-eclipse'>Eclipse Update Site</h4>
-<div class="section-content">
-<p>
-          Podlings may distribute suitable artifacts through an 
-          <a href="http://www.eclipse.org">Eclipse</a> update site.
-          All artifacts distributed through the update site must satisfy the standard
-          <a href="#distribution-policy-overview">policy</a>. This implies that:
-          </p>
-<ul>
-            <li>The update site must be contained within the  
-            <a href="#glossary-podling-dist">podling distribution directory</a>.</li>
-            <li>All artifacts must be 
-            <a href="http://www.apache.org/dev/release-signing.html#keys-policy">signed
and summed</a>.</li>
-            <li><a href="#distribution-mirroring">Mirroring</a> must be
used.</li>
-          </ul>
-<p>Detailed instructions on how to setup an Incubator Project to have an 
-            <a href="releasing-eclipse-update-site.html">Eclipse update site with Mirroring</a>
are available.</p>
-</div>
 </div>
 </div>
         <h2 id='check-list'><img src="../images/redarrow.gif" />Check List</h2>
@@ -1402,7 +1338,6 @@ lists. Subscribe to:
     	</p>
 <ul>
             <li><em>legal-discuss</em> for matters related to licensing</li>
-            <li><em>repository</em> for matters related to the maven repositories</li>
             <li><em>infrastructure-issues</em> for matters related to </li>
         </ul>
 </div>
@@ -1443,22 +1378,6 @@ So typically, the release manager needs 
 A release is a good time to concentrate energy on documentation.
     		</p>
 </div>
-<h3 id='best-practice-jars'>Jars</h3>
-<div class="section-content">
-<ul>
-                <li><code>META-INF</code>
-                    <ul>
-                        <li>
-    Must include <a href="#license">LICENSE</a> and <a href="#NOTICE">NOTICE</a>.

-    Note <a href="#distributing-jars">this</a>
-                        </li>
-                        <li>
-    Should include a standards compliant MANIFEST. Note <a href="#jar-manifest">this</a>.
-                        </li>
-                    </ul>
-                </li>
-            </ul>
-</div>
 <h3 id='best-practice-naming'>Artifact Naming</h3>
 <div class="section-content">
 <p>
@@ -1673,14 +1592,6 @@ into the current directory). The directo
 the standard naming convention. apache-foo.tar.gz should unpack to the apache-foo
 directory.
             </p>
-<p>
-Note (TODO link) that there are known compatibility issues when using certain tar programs.

-(TODO Saris verses GNU tar)
-It is recommend that project that use Ant or Maven as build tools, use these tools to create
-the archives since these implementations work well across a range of platforms. 
-It is recommended that project which do not use these tools consider shipping the
-*nix package as a bz2 archive.
-            </p>
 </div>
 <h3 id='best-practice-source-build'>Source Package Build</h3>
 <div class="section-content">
@@ -1692,9 +1603,6 @@ Source packages should contain easy inst
 The source package should build from instructions contained. 
 TODO: best practices for instructing users about building the project.
             </p>
-<p>
-Build instructions should give supported version numbers for build tools (for example, maven
and ant).
-            </p>
 </div>
 <h3 id='best-practice-dependencies'>Dependencies</h3>
 <div class="section-content">
@@ -1729,9 +1637,6 @@ dependencies.
 TODO: ASF policy compliance
 TODO: project policy - explicit policy should be written down
             </p>
-<p>
-TODO: Discussion on the merits of distributing dependent jars. This should be a link to the
notes section
-            </p>
 </div>
 <h3 id='best-practice-notice'>NOTICE files</h3>
 <div class="section-content">
@@ -1831,8 +1736,7 @@ As well as libraries, projects often hav
 Most languages have different versions, and it is important that the versions
 of a language upon which a project will build and run are clearly documented.
 The <a href="TODO:">release notes</a>
-are a typical location for this information. <a href="TODO:link to note on ">Note</a>
-that Java also includes the version used to build in the MANIFEST. 
+are a typical location for this information.
         	</p>
 <p>
 It is important to review all library dependencies as part of the release process
@@ -1949,27 +1853,6 @@ Please remember to delete release candid
  isolated installation to store the code signing key and to sign releases.
         	</p>
 </div>
-<h3 id='best-practice-maven'>Maven</h3>
-<div class="section-content">
-<p>
-<a href="http://maven.apache.org">Apache Maven</a> is a tool used by many podlings.
-TODO: improve preamble
-        	</p>
-<p>
-It is best to use the <code>groupId</code> and <code>artifactId</code>
that will
-be used upon graduation. The version should include <code>incubating</code> 
-(or <code>incubator</code>) to ensure that the artifacts created comply with
Incubator
-<a href="../incubation/Incubation_Policy.html#Releases">release policy</a>.
-        	</p>
-<p>
-For example
-        	</p>
-<code><pre>
-	&lt;groupId&gt;org.apache.wicket&lt;/groupid&gt;
-	&lt;artifactId&gt;wicket-parent&lt;/artifactId&gt;
-	&lt;version&gt;1.3-incubating-SNAPSHOT&lt;/version&gt;
-</pre></code>
-</div>
 </div>
         <h2 id='notes'><img src="../images/redarrow.gif" />Notes</h2>
 <div class="section-content">
@@ -1992,43 +1875,6 @@ TODO: complete content
             DISCLAIMER. It is recommended that it is not included in NOTICES
             </p>
 </div>
-<h3 id='distributing-jars'>Distributing Jars</h3>
-<div class="section-content">
-<p>
-            TODO: link to infrastructure
-            </p>
-<p>
-Jars are just another form of binary package. If they are likely to be distributed
-(for example, through the Apache Repository) then they must adhere to the same policy
-as other binary packages. 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 id='jar-manifest'>Jar MANIFEST</h3>
-<div class="section-content">
-<p>
-TODO
-Lots of projects get this wrong and most tools, by default, produce substandard manifests.
-Offer some guidance on values
-TODO: Add how to create a specification compliant MANIFEST 
-http://jakarta.apache.org/commons/releases/prepare.html#checkjarmanifest
-            </p>
-<p>
-Maven 1 produces a minimal MANIFEST. This should be augmented 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 manifest entries. 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 recommended entries.
-            </p>
-</div>
 <h3 id='best-practice-release-candidate'>Release Candidates</h3>
 <div class="section-content">
 <p>
@@ -2212,20 +2058,6 @@ This may be included by reference to the
 but (for the benefit of those that don't read document) should be mentioned.
 			</p>
 </div>
-<h3 id='note-compatibility-checkers'>Compatibility Checkers</h3>
-<div class="section-content">
-<p>
-Some tools used by Apache projects:
-			</p>
-<ul>
-				<li>Java
-					<ul>
-						<li><a href="http://clirr.sourceforge.net//">Clirr</a> works on binaries</li>
-						<li><a href="http://jdiff.sourceforge.net/">JDiff</a> uses sources</li>
-					</ul>
-				</li>
-			</ul>
-</div>
 <h3 id='notes-change-log'>Change Logs</h3>
 <div class="section-content">
 <p>
@@ -2236,7 +2068,6 @@ TODO: add examples
 A change log indicates the changes made to the project since the last release.
 Some projects include a change log in the release notes documents.
 Others use a separate document often called <code>ChangeLog</code>.
-Maven can be used to generate a change log as part of the project documentation.
         	</p>
 <p>
 Change logs can be created in various ways. Some project ask committers to fill
@@ -2309,44 +2140,6 @@ If not then consider adding a NOTE or a 
 than a license header.
         	</p>
 </div>
-<h3 id='notes-on-java-version'>On Java Versions</h3>
-<div class="section-content">
-<p>
-Indicating supported versions for dependencies is 
-<a href="#best-practice-dependencies">important</a>. The minimum 
-(and - where appropriate - maximum)  Java version need to be clearly documented
-in the release. This information should be included in a README or the RELEASE NOTES.
-        	</p>
-<p>
- Users often expect the minimum version supported to be the one listed in the MANIFEST.
- There are also good reasons for releases to be compiled with the minimum version 
- of Java supported by the release. This is the easiest way to ensure that the release
- will work as expected on that version. This will ensure that the version in the MANIFEST
- is as expected. 
- 			</p>
-<p>
-If the version in the MANIFEST cannot reflect the minimum support version (see below) 
-then it is recommended that the flowing additional entries are added to MANIFEST.
- 			</p>
-<p>
-The usual reason for need to use a more modern Java version is to support
-optional classes which require features present only in the new version.
-			</p>
-<p>
-The approach which requires the least configuration is to adopt a split compilation
-strategy. The release manager installs two separate Java versions. The build
-script supports optional parameterization allowing the optional code to be compiled with

-a second JSDK. It is recommended that the build scrip includes clear indications
-that a second JSDK has been detected.
- 			</p>
-<p>
-The alternative is to correctly configure a more modern JSDK to compile code
-which will function correctly on another JRE. This means TODO: javac settings through 
-Ant. This is not sufficient. Unfortunately the source also need to be compiled against
-the appropriate version of the Java API. TODO: check where the jar has to be exactly
-placed.
-        	</p>
-</div>
 <h3 id='notes-on-export-regulations'>On Export Regulations</h3>
 <div class="section-content">
 <p>
@@ -2365,9 +2158,7 @@ It is convenient for users and more cons
 for the <code>zip</code> and <code>LF</code> for the <code>tar.gz</code>).
         	</p>
 <p>
-Source packages can use <code>svn export --native-es</code>. Binary packages
-build with <a href="http://ant.apace.org">Ant</a> can use 
-<a href="http://ant.apache.org/manual/CoreTasks/fixcrlf.html">fixcrlf</a>.
+Source packages can use <code>svn export --native-es</code>.
             </p>
 </div>
 <h3 id='notes-press-releases'>On Press Releases</h3>
@@ -2381,20 +2172,6 @@ press interest in a release then please 
 TODO: link to public relations committee
         	</p>
 </div>
-<h3 id='notes-on-signing-jars'>On Signing Jars</h3>
-<div class="section-content">
-<p>
-Java includes a standard mechanism for signing jars. Apache uses digital
-signatures to protect releases. TODO: reconsider this section.
-        	</p>
-<p>
-Though there is no rule against issuing signed jars, project should educate
-themselves about the potentially negative consequences of doing so.
-Classloaders treat signed jars differently. In particular, packages are 
-sealed against modification. Open source encourages modification. 
-TODO: rephrase and check
-        	</p>
-</div>
 <h3 id='notes-license-headers'>On License Headers</h3>
 <div class="section-content">
 <p>
@@ -2459,13 +2236,6 @@ in the directory containing license info
 TODO: importance of accurately reporting to the user the state of an implementation
 TODO: importance of complying with the reporting requirements set by the standard creator
         	</p>
-<h4 id='notes-jsr'>JSRs</h4>
-<div class="section-content">
-<p>
-TODO: write up http://marc.theaimsgroup.com/?l=incubator-general&amp;m=116577422312412&amp;w=2
-TODO: then check with Geir
-        		</p>
-</div>
 </div>
 <h3 id='note-license-and-notice'>Understanding Content For NOTICE and LICENSE</h3>
 <div class="section-content">
@@ -2634,23 +2404,6 @@ This allows people to check their votes 
  release candidate).
         	</p>
 </div>
-<h3 id='notes-release-candidate-java'>On Java Release Candidates</h3>
-<div class="section-content">
-<p>
-This section applies to any package that contains re-distributable artifacts which contain
version
-information but in particular binary packages of Java contain jar files. A compliant MANIFEST

-meta data file within each of these files should contain the implementation version.
-These are good reasons to use the release version number as the implementation version.
-This allows the exact version to be determined from just the jar.
-Unfortunately, some applications expect the format to be entirely numeric (TODO: maven?)
-			</p>
-<p>
-This does mean that release candidates for binary packages of this type must either
-be rereleased with the version number as the only change or accept that artifacts will not
be 
-uniquely named. Uncertainty about exact jar versions has caused nasty dependency
-issues in the past.
-			</p>
-</div>
 <h3 id='notes-on-gnu-tar'>GNU Tar Known Incompatibilities</h3>
 <div class="section-content">
 <p>
@@ -2757,15 +2510,6 @@ are only intended for people participati
         	TODO: link to foundation docs
         	</p>
 </div>
-<h3 id='glossary-manifest'>Jar MANIFEST</h3>
-<div class="section-content">
-<p>
-Meta data, enumerating the contents of the Jar, associated with the Java Jar format.
-        	</p>
-<p>
-            TODO link to sun documentation
-            </p>
-</div>
 <h3 id='glossary-license-header'>License Header</h3>
 <div class="section-content">
 <p>

Modified: websites/staging/incubator/trunk/content/report-next-month.html
==============================================================================
--- websites/staging/incubator/trunk/content/report-next-month.html (original)
+++ websites/staging/incubator/trunk/content/report-next-month.html Mon Aug  6 03:33:01 2012
@@ -67,7 +67,7 @@
 <h1>
 <a href="http://incubator.apache.org">Apache Incubator</a> Podlings needing to
prepare report for September</h1>
 <div style="text-align:right;">
-<i>Generated on 2012-08-06T03:32:21Z</i>
+<i>Generated on 2012-08-06T03:33:15Z</i>
 </div>
 <nav>
 <ul>

Modified: websites/staging/incubator/trunk/content/sitemap.html
==============================================================================
--- websites/staging/incubator/trunk/content/sitemap.html (original)
+++ websites/staging/incubator/trunk/content/sitemap.html Mon Aug  6 03:33:01 2012
@@ -1235,9 +1235,6 @@ Site map of <a href="http://incubator.ap
 <li>
 <a href="guides/releasemanagement.html#distribution-defects">Dealing With A Defect</a>
 </li>
-<li>
-<a href="guides/releasemanagement.html#distributing-eclipse">Eclipse Update Site</a>
-</li>
 </ul>
 </li>
 </ul>
@@ -1275,9 +1272,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#best-practice-prepare-documentation">Preparing
Documentation</a>
 </li>
 <li>
-<a href="guides/releasemanagement.html#best-practice-jars">Jars</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#best-practice-naming">Artifact Naming</a>
 </li>
 <li>
@@ -1346,9 +1340,6 @@ Site map of <a href="http://incubator.ap
 <li>
 <a href="guides/releasemanagement.html#signing-releases">Signatures</a>
 </li>
-<li>
-<a href="guides/releasemanagement.html#best-practice-maven">Maven</a>
-</li>
 </ul>
 </li>
 <li>
@@ -1361,12 +1352,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#notes-disclaimer">The Incubator Disclaimer</a>
 </li>
 <li>
-<a href="guides/releasemanagement.html#distributing-jars">Distributing Jars</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#jar-manifest">Jar MANIFEST</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#best-practice-release-candidate">Release Candidates</a>
 </li>
 <li>
@@ -1382,9 +1367,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#release-notes">Release Notes</a>
 </li>
 <li>
-<a href="guides/releasemanagement.html#note-compatibility-checkers">Compatibility Checkers</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#notes-change-log">Change Logs</a>
 </li>
 <li>
@@ -1397,9 +1379,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#notes-on-templates">On Template Sources</a>
 </li>
 <li>
-<a href="guides/releasemanagement.html#notes-on-java-version">On Java Versions</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#notes-on-export-regulations">On Export Regulations</a>
 </li>
 <li>
@@ -1412,9 +1391,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#notes-press-releases">On Press Releases</a>
 </li>
 <li>
-<a href="guides/releasemanagement.html#notes-on-signing-jars">On Signing Jars</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#notes-license-headers">On License Headers</a>
 </li>
 <li>
@@ -1422,11 +1398,6 @@ Site map of <a href="http://incubator.ap
 </li>
 <li>
 <a href="guides/releasemanagement.html#note-standards">Implementations Of Standards</a>
-<ul>
-<li>
-<a href="guides/releasemanagement.html#notes-jsr">JSRs</a>
-</li>
-</ul>
 </li>
 <li>
 <a href="guides/releasemanagement.html#note-license-and-notice">Understanding Content
For NOTICE and LICENSE</a>
@@ -1443,9 +1414,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#notes-revote">On Managing VOTE Threads</a>
 </li>
 <li>
-<a href="guides/releasemanagement.html#notes-release-candidate-java">On Java Release
Candidates</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#notes-on-gnu-tar">GNU Tar Known Incompatibilities</a>
 </li>
 <li>
@@ -1478,9 +1446,6 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#glossary-ceremony">Ceremony</a>
 </li>
 <li>
-<a href="guides/releasemanagement.html#glossary-manifest">Jar MANIFEST</a>
-</li>
-<li>
 <a href="guides/releasemanagement.html#glossary-license-header">License Header</a>
 </li>
 <li>



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


Mime
View raw message