incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r891973 - in /websites/staging/incubator/trunk/content: ./ guides/releasemanagement.html report-next-month.html sitemap.html
Date Sat, 28 Dec 2013 17:48:20 GMT
Author: buildbot
Date: Sat Dec 28 17:48:19 2013
New Revision: 891973

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 Sat Dec 28 17:48:19 2013
@@ -1 +1 @@
-1553723
+1553877

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 Sat Dec 28 17:48:19
2013
@@ -191,6 +191,14 @@ Guidelines
 Distributing Releases
  </a>
  <ul>
+<li><a href='#glossary-incubator-dist'>
+Incubator Distribution Directory
+ </a>
+</li>
+<li><a href='#glossary-podling-dist'>
+Podling Distribution Directory
+ </a>
+</li>
 <li><a href='#distribution-policy-overview'>
 Policy Overview
  </a>
@@ -520,92 +528,6 @@ On Binary-Only Releases
 <li><a href='#glossary'>
 Glossary
  </a>
- <ul>
-<li><a href='#glossary-cla'>
-Contributor License Agreement
- </a>
-</li>
-<li><a href='#glossary-ccla'>
-Contributor License Agreement - Corporate
- </a>
-</li>
-<li><a href='#glossary-artifact'>
-Distributed Artifact
- </a>
-</li>
-<li><a href='#glossary-license'>
-LICENSE file
- </a>
-</li>
-<li><a href='#glossary-notice'>
-NOTICE file
- </a>
-</li>
-<li><a href='#glossary-ceremony'>
-Ceremony
- </a>
-</li>
-<li><a href='#glossary-license-header'>
-License Header
- </a>
-</li>
-<li><a href='#glossary-release-manager'>
-Release Manager
- </a>
-</li>
-<li><a href='#glossary-release-candidate'>
-Release Candidate
- </a>
-</li>
-<li><a href='#glossary-package'>
-Package
- </a>
-</li>
-<li><a href='#glossary-artifact'>
-Artifact
- </a>
-</li>
-<li><a href='#glossary-package-type'>
-Package Type
- </a>
-</li>
-<li><a href='#glossary-source-package'>
-Source Package
- </a>
-</li>
-<li><a href='#glossary-binary-package'>
-Binary Package
- </a>
-</li>
-<li><a href='#glossary-guidelines'>
-Guidelines
- </a>
-</li>
-<li><a href='#glossary-release-documentation'>
-Release Documentation
- </a>
-</li>
-<li><a href='#glossary-ipmc'>
-Incubator Project Management Committee (Incubator PMC)
- </a>
-</li>
-<li><a href='#glossary-ppmc'>
-Podling Project Management Committee (Podling PMC)
- </a>
-</li>
-<li><a href='#glossary-pmc'>
-Project Management Committee
- </a>
-</li>
-<li><a href='#glossary-incubator-dist'>
-Incubator Distribution Directory
- </a>
-</li>
-<li><a href='#glossary-podling-dist'>
-Podling Distribution Directory
- </a>
-</li>
-</ul>
 </li>
 </ul>
 </div>
@@ -830,6 +752,30 @@ maintained on the <a href="http://wiki.a
              distributing a release, esp. when your release artifacts are huge.
          </p>
      </div>
+<h3 id='glossary-incubator-dist'>Incubator Distribution Directory</h3>
+<div class="section-content">
+<p>
+All Incubator authorised by the incubator are contained within the
+Incubator distribution directory:
+          </p>
+<div class="source"><code>
+https://dist.apache.org/repos/dist/release/incubator
+</code>
+</div>
+</div>
+<h3 id='glossary-podling-dist'>Podling Distribution Directory</h3>
+<div class="section-content">
+<p>
+All releases created by a podling are contained within a sub-directory of the
+<a href="#glossary-incubator-dist">Incubator distribution directory</a>.
+This is <code>www.apache.org/dist/incubator/{podling}</code> where <em>{podling}</em>

+is the name of the podling.
+          </p>
+<p>
+For example, the podling distribution directory for podling <code>foo</code>
is
+            <code>https://dist.apache.org/repos/dist/release/incubator/foo</code>.
+          </p>
+</div>
 <h3 id='distribution-policy-overview'>Policy Overview</h3>
 <div class="section-content">
 <p>
@@ -1360,10 +1306,9 @@ So, it is of particular importance that 
         <h2 id='release-guidelines'><img src="../images/redarrow.gif" />Release
Guidelines</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 flow
-these guidelines but they have not been blessed as policy.
+In addition to policy, the infrastructure, public relations and legal teams also document
"guidelines" for projects:
+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>
 <p>
 Guidelines change much more frequently than policy. Release managers should follow the appropriate
@@ -1379,8 +1324,8 @@ lists. Subscribe to:
 <h3 id='best-practice-preparation'>Preparation</h3>
 <div class="section-content">
 <p>
-Preparation is the key to quality. The <a href="#glossary-release-manager">release
manager</a>
-will need to organise and coordinate this but need not execute all.
+Preparation is the key to quality. The <a href="http://www.apache.org/foundation/glossary.html#ReleaseManager">release
+manager</a> will need to organise and coordinate this but need not execute all.
             </p>
 <ul>
 				<li>Analyze <a href="#best-practice-prepare-documentation">bugs</a></li>
@@ -1488,7 +1433,7 @@ For others, it does not.
 <h3 id='best-practice-documentation'>Release Documentation</h3>
 <div class="section-content">
 <p>
-Users expect <a href="#glossary-release-documentation">release documentation</a>

+Users expect release documentation
 to be present in the root directory of the package. If copies of these documents are required
 elsewhere, it is recommended that the release process creates copies. These documents
 should be present in all <a href="#best-practice-types">types of packages</a>
@@ -1680,7 +1625,7 @@ This must include:
              </ul>
 <p>
 Every contributor retains the copyright to their contributions and grants Apache only a (generous)
-license for the work. A release is an act of selection by the <a href="#glossary-pmc">PMC</a>.
Apache holds the copyright
+license for the work. A release is an act of selection by the <a href="http://www.apache.org/foundation/glossary.html#PMC">PMC</a>.
Apache holds the copyright
 to the collective work that is the release. The Apache copyright in the <code>NOTICE</code>
 pertains to the collective.
              </p>
@@ -1905,7 +1850,8 @@ TODO: complete content
 <h3 id='best-practice-release-candidate'>Release Candidates</h3>
 <div class="section-content">
 <p>
-There are two distinct approaches: <a href="#glossary-release-candidate">release candidate</a>
and TODO.  
+There are two distinct approaches: <a href="http://www.apache.org/foundation/glossary.html#ReleaseCandidate">release
+candidate</a> and TODO.  
         	</p>
 </div>
 <h3 id='best-practice-versioning'>Versioning</h3>
@@ -2364,9 +2310,8 @@ example</a>. 
 			</p>
 <p>
 Be careful to check the voters against the appropriate list. Binding votes are cast by people
on the 
-appropriate committee. The list of <a href="#glossary-ipmc">Incubator PMC</a>ers
is 
-<a href="http://incubator.apache.org/whoweare.html">available</a> TODO: link
online. Note that 
-sometimes the online lists are out of date. TODO: link to foundation site.
+appropriate committee. The list of Incubator PMC members is 
+<a href="http://people.apache.org/committers-by-project.html#incubator-pmc">available</a>.
 			</p>
 <p>
 The result post should list each voter and the vote cast. Non binding votes may be listed.
If they are 
@@ -2394,8 +2339,8 @@ a . There is usually no need for this vo
 be a -1 due to a nearly discovered security issue, for example.)
         		</p>
 <p>
-In the case of podlings, a 3 binding +1s are required by members of the <a href="#glossary-ipmc">Incubator
-PMC</a>. To increase the chances of a prompt approval, mentors need to cast their
+In the case of podlings, a 3 binding +1s are required by members of the Incubator
+PMC. To increase the chances of a prompt approval, mentors need to cast their
 votes on the general list.
         		</p>
 </div>
@@ -2462,284 +2407,26 @@ project needs to recruit new developers 
 </div>
         <h2 id='glossary'><img src="../images/redarrow.gif" />Glossary</h2>
 <div class="section-content">
-<h3 id='glossary-cla'>Contributor License Agreement</h3>
-<div class="section-content">
-<p>
- A Contributor License Agreement (CLA) is a contract between a contributor
- and Apache granting Apache rights to code contributed. Every committer
- must have a signed CLA on file.
-            </p>
-<p>
-See
-            </p>
-<ul>
-                <li>
-<a href="http://www.apache.org/licenses/icla.txt">CLA text</a>
-                </li>
-                <li>
-                  <a href="http://www.apache.org/licenses/#clas">explanation</a>
-                  of license agreements
-                </li>
-            </ul>
-</div>
-<h3 id='glossary-ccla'>Contributor License Agreement - Corporate</h3>
-<div class="section-content">
-<p>
- A Corporate Contributor License Agreement (CCLA) is a contract between a corporation
- and Apache granting Apache rights to code contributed by its employees. Some legal
- jurisdications do not allow software developers rights to code created even in their own
- time on their own machines. This applies to most US developers. A CCLA protected Apache
- and .
-            </p>
-<p>
-See
-            </p>
-<ul>
-                <li>
-<a href="http://www.apache.org/licenses/cla-corporate.txt">CCLA text</a>
-                </li>
-                <li>
-                  <a href="http://www.apache.org/licenses/#clas">explanation</a>
-                  of license agreements
-                </li>
-            </ul>
-</div>
-<h3 id='glossary-artifact'>Distributed Artifact</h3>
-<div class="section-content">
-<p>
-A file that is actually made available for download.  Note this does <strong>NOT</strong>
imply
-the file is intended for wide-scale distribution to the general public.  Such
-distributions are reserved for formally-approved releases.  For instance artifacts
-included in release candidates, periodic builds, and even the code repository itself,
-are only intended for people participating in project development.
-        	</p>
-<p>
-            TODO (include link to infra documentation)
-            </p>
-</div>
-<h3 id='glossary-license'>LICENSE file</h3>
-<div class="section-content">
-<p>
-  Document containing the licenses for the package.
-        	</p>
-</div>
-<h3 id='glossary-notice'>NOTICE file</h3>
-<div class="section-content">
-<p>
-  Document containing additional required copyright and attribute information.
-            </p>
-</div>
-<h3 id='glossary-ceremony'>Ceremony</h3>
-<div class="section-content">
-<p>
-        	Process and procedure associated with - but not necessary to - a particular end.
-        	TODO: link to foundation docs
-        	</p>
-</div>
-<h3 id='glossary-license-header'>License Header</h3>
-<div class="section-content">
-<p>
-Text referring to the license for a file (as opposed to the license text).
-         	</p>
-<p>
-            TODO (include link to legal documentation)
-            </p>
-</div>
-<h3 id='glossary-release-manager'>Release Manager</h3>
-<div class="section-content">
-<p>
-Committer responsible for shepherding the release.  This role is rather time consuming
-and often involves tedious tasks, but it is essential that the release manager keep
-on top of everything.  Release managers may be elected for a release by the project
-by formal vote, or by invoking lazy consensus, but such votes are not really necessary.
-A procedural description of the role as it functions within the incubator follows.
-        	</p>
-<p>
-Once a release manager has stepped forward, the first thing they should do is to
-consult and correct the project's <a href="#glossary-release-documentation">release
-documentation</a>.  Once that has been addressed, the candidate artifacts should be
-prepared and a formal vote on those artifacts must be conducted by the release manager
-on the project's development list.  [Note: this must be followed by a vote on the
-general@incubator list - see below.] All votes are welcome, but only those votes by the
-project's <a href="#glossary-ppmc">PPMC</a> members (or <a href="#glossary-ipmc">IPMC</a>
-members) count towards the final tally.  The voting period should be no less than 72
-hours, and at the end of the voting the release manager should post a final tally to the
list.
-                </p>
-<p>
-The PPMC vote passes if there are at least 3 +1's from the PPMC/IPMC members and more
-+1's than -1's.  This is what is meant by majority consensus.
-                </p>
-<p>
-It is Apache policy that all releases be formally approved by the responsible PMC.
-In the case of the incubator, the IPMC must approve all releases.  That means there
-is an additional bit of voting that the release manager must now oversee on
-general@incubator in order to gain that approval.  The release manager must inform
-general@incubator that the vote has passed on the podling's development list, and
-should indicate any IPMC votes gained during that process.  A new vote on the
-release candidate artifacts must now be held on general@incubator to seek majority
-consensus from the IPMC.  Previous IPMC votes issued on the project's development
-list count towards that goal. Even if there are sufficient IPMC votes already, it is
-vital that the IPMC as whole is informed via a VOTE e-mail on general@incubator.
-                </p>
-<p>
-Once the 72-hour minimum voting period has ended on general@incubator, the release
-manager should tally the votes and declare a result.  If majority consensus has
-been achieved with respect to IPMC votes, the release manager may proceed with the
-release.  Read the remainder of this document for details on the remaining steps
-regarding uploading artifacts to the podling's distribution directory, dealing with
-downstream distribution channels if appropriate, and announcing the release to
-the public.
-                </p>
-<p>
-            TODO (include link to infra documentation)
-            TODO say something about the technical release manager (who
-            cuts the release) and the social one (who organizes it).
-            </p>
-</div>
-<h3 id='glossary-release-candidate'>Release Candidate</h3>
-<div class="section-content">
-<p>
-Collection of artifacts to be tested and voted on in order to release them.  Sometimes
-folks use this term to refer only to a candidate source package.
-            </p>
-</div>
-<h3 id='glossary-package'>Package</h3>
-<div class="section-content">
-<p>
-        A file created from a project's source code with the intent to distribute.  Note
-        this is not to be confused with the notion of a
-        <a href="http://www.google.com/search?q=define:Java+package">Java package</a>,
-        or however else the word "package" may be used by any specific programming language
community.
-        Here we use it in the generic sense to refer to software packages.
-            </p>
-</div>
-<h3 id='glossary-artifact'>Artifact</h3>
-<div class="section-content">
-<p>
-            Artifact is a generic term for a package, or more generally a file of any kind.
-            </p>
-</div>
-<h3 id='glossary-package-type'>Package Type</h3>
-<div class="section-content">
-<p>
-Packages are typically either source packages or binary packages (i.e. builds).
-Sometimes separate documentation packages are released alongside the source package.
-            </p>
-</div>
-<h3 id='glossary-source-package'>Source Package</h3>
-<div class="section-content">
-<p>
-A source package is typically a compressed archive file containing a 
-simple export from the repository, optionally with some preconfiguration
-scripts run on it.
-            </p>
-</div>
-<h3 id='glossary-binary-package'>Binary Package</h3>
-<div class="section-content">
-<p>
-Binary packages are typically platform-specific builds of the source package.
-There is only one canonical source package but there may be several binary packages.
-            </p>
-</div>
-<h3 id='glossary-guidelines'>Guidelines</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>
-<h3 id='glossary-release-documentation'>Release Documentation</h3>
-<div class="section-content">
-<p>
-Documents a particular release of a product rather than the product itself.
-Note that release documentation also occasionally refers to the instructions for the
-release manager to follow during the process of creating a release.
-                </p>
-</div>
-<h3 id='glossary-ipmc'>Incubator Project Management Committee (Incubator PMC)</h3>
-<div class="section-content">
-<p>
- The committee charged by the <a href="http://www.apache.org/foundation/board/">board</a>

- with the management of the Apache Incubator Project.
-            </p>
 <p>
- See also:
-            </p>
-<ul>
-                <li>
-<a href="#glossary-pmc">PMC</a>
-                </li>
-                <li>
- <a href="http://incubator.apache.org/whoweare.html">Who Are The Incubator PMC members?</a>
-                </li>
-                <li>
-  <a href="http://incubator.apache.org/guides/pmc.html">Guide For Incubator PMC members</a>
-                </li>
-            </ul>
-</div>
-<h3 id='glossary-ppmc'>Podling Project Management Committee (Podling PMC)</h3>
-<div class="section-content">
-<p>
-The group of committers charged with development and direction of a podling.  Not a formally
recognized
-Apache committee- that only happens once the podling graduates.  The active Podling PMC members
form
-the seed for a formal PMC if the project graduates to a top-level Apache project; otherwise
the active
-Podling PMC members join a pre-existing PMC to continue development as a subproject of that
PMC.
-            </p>
-</div>
-<h3 id='glossary-pmc'>Project Management Committee</h3>
-<div class="section-content">
-<p>
- A committee charged by the <a href="http://www.apache.org/foundation/board/">board</a>

- with the management of an <a href="http://projects.apache.org/">Apache Project</a>.
-            </p>
-<p>
- See also:
-            </p>
-<ul>
-                <li>
- <a href="http://www.apache.org/foundation/how-it-works.html">How Apache works</a>
-                </li>
-                <li>
- <a href="http://www.apache.org/dev/#pmc">Apache information for PMCs</a>
-                </li>
-             </ul>
-</div>
-<h3 id='glossary-incubator-dist'>Incubator Distribution Directory</h3>
-<div class="section-content">
-<p>
-All Incubator authorised by the incubator are contained within the
-Incubator distribution directory:
-          </p>
-<div class="source"><code>
-https://dist.apache.org/repos/dist/release/incubator
-</code>
-</div>
-</div>
-<h3 id='glossary-podling-dist'>Podling Distribution Directory</h3>
-<div class="section-content">
-<p>
-All releases created by a podling are contained within a sub-directory of the
-<a href="#glossary-incubator-dist">Incubator distribution directory</a>.
-This is <code>www.apache.org/dist/incubator/{podling}</code> where <em>{podling}</em>

-is the name of the podling.
-          </p>
-<p>
-For example, the podling distribution directory for podling <code>foo</code>
is
-            <code>https://dist.apache.org/repos/dist/release/incubator/foo</code>.
-          </p>
-<p>
-See also:
-          </p>
-<ul>
-            <li>
-            <a href="#distribution-policy-overview">Distribution policy overview</a>
-            </li>
-            <li>
-            <a href="#understanding-upload">Uploading packages</a>
-            </li>
-          </ul>
-</div>
+<!-- Old glossary links -->
+<a id="glossary-artifact" />
+<a id="glossary-binary-package" />
+<a id="glossary-ceremony" />
+<a id="glossary-cla" />
+<a id="glossary-ccla" />
+<a id="glossary-guidelines" />
+<a id="glossary-ipmc" />
+<a id="glossary-license-header" />
+<a id="glossary-license" />
+<a id="glossary-package" />
+<a id="glossary-package-type" />
+<a id="glossary-pmc" />
+<a id="glossary-notice" />
+<a id="glossary-release-candidate" />
+<a id="glossary-release-manager" />
+<a id="glossary-source-package" />
+The Incubator's Glossary has been removed.  Much of the content which once lived here has
been consolidated into the <a href="http://www.apache.org/foundation/glossary.html">main
ASF glossary</a>.
+      </p>
 </div>
        </div>
    </div>

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 Sat Dec 28 17:48:19 2013
@@ -67,7 +67,7 @@
 <h1>
 <a href="http://incubator.apache.org">Apache Incubator</a> Podlings needing to
prepare report for January</h1>
 <div style="text-align:right;">
-<i>Generated on 2013-12-27T19:20:16Z</i>
+<i>Generated on 2013-12-28T17:46:52Z</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 Sat Dec 28 17:48:19 2013
@@ -1242,6 +1242,12 @@ Site map of <a href="http://incubator.ap
 <a href="guides/releasemanagement.html#release-distribution">Distributing Releases</a>
 <ul>
 <li>
+<a href="guides/releasemanagement.html#glossary-incubator-dist">Incubator Distribution
Directory</a>
+</li>
+<li>
+<a href="guides/releasemanagement.html#glossary-podling-dist">Podling Distribution
Directory</a>
+</li>
+<li>
 <a href="guides/releasemanagement.html#distribution-policy-overview">Policy Overview</a>
 </li>
 <li>
@@ -1492,71 +1498,6 @@ Site map of <a href="http://incubator.ap
 </li>
 <li>
 <a href="guides/releasemanagement.html#glossary">Glossary</a>
-<ul>
-<li>
-<a href="guides/releasemanagement.html#glossary-cla">Contributor License Agreement</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-ccla">Contributor License Agreement
- Corporate</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-artifact">Distributed Artifact</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-license">LICENSE file</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-notice">NOTICE file</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-ceremony">Ceremony</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-license-header">License Header</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-release-manager">Release Manager</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-release-candidate">Release Candidate</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-package">Package</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-artifact">Artifact</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-package-type">Package Type</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-source-package">Source Package</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-binary-package">Binary Package</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-guidelines">Guidelines</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-release-documentation">Release Documentation</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-ipmc">Incubator Project Management
Committee (Incubator PMC)</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-ppmc">Podling Project Management Committee
(Podling PMC)</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-pmc">Project Management Committee</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-incubator-dist">Incubator Distribution
Directory</a>
-</li>
-<li>
-<a href="guides/releasemanagement.html#glossary-podling-dist">Podling Distribution
Directory</a>
-</li>
-</ul>
 </li>
 </ul>
 </li>



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


Mime
View raw message