incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1449969 - /incubator/public/trunk/content/guides/releasemanagement.xml
Date Mon, 25 Feb 2013 23:44:26 GMT
Author: marvin
Date: Mon Feb 25 23:44:25 2013
New Revision: 1449969

Remove common terms from the glossary.

*   "issue tracker" is an industry standard term.
*   "ceremony" is not commonly used in either the ASF or the Incubator.
*   "cutting the release" is ambiguous (is it cutting an RC or
    publishing a release?) and attempts to formalize its meaning in a
    glossary are unlikely to stamp out conflicting usage.


Modified: incubator/public/trunk/content/guides/releasemanagement.xml
--- incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] Mon Feb 25 23:44:25
@@ -201,7 +201,7 @@ usually consider a <em>faux pas</em>.
 In the early stages of a release, they should take responsibility for organizations,
 in the middle stages of a release, for deciding which code will be included in the release,
 in the late stages for marshaling the VOTEs required for formal approval
-then finally for <a href='#glossary-cutting-release'>cutting the release</a>.
+then finally for cutting the release.
 TODO: maybe be better in a time line
@@ -1573,8 +1573,7 @@ provenance of the code traceable. 
 Commit comments are an important to. When source
 which is not originally created for the project is committed, the message should contain
 details about the provenance of that source. When a patch is applied from an 
-<a href='#glossary-issue-tracker'>issue tracking system</a>
-system, the issue should be noted in the commit message. 
+issue tracking system, the issue should be noted in the commit message. 
 Releases are important. Released code is distributed widely. It is important that the provenance
@@ -1954,13 +1953,6 @@ Binary packages are typically platform-s
 There is only one canonical source package but there may be several binary packages.
-        <section id='glossary-cutting-release'><title>Cutting The Release</title>
-        	<p>
-The actual execution of the release. Typically consists of building the packages
-from the repository tag, along with any other associated artifacts, and signing them.
-TODO: link to infra
-        	</p>
-        </section>
         <section id='glossary-guidelines'><title>Guidelines</title>
 Guidelines are documented recommendations which have not yet been blessed as policy.
@@ -1976,11 +1968,6 @@ release manager to follow during the pro
-        <section id='glossary-issue-tracker'><title>Issue Tracking System</title>
-        	<p>
-An application that store manages issues reported in Apache products. TODO: links
-        	</p>
-        </section>
         <section id='glossary-ipmc'><title>Incubator Project Management Committee
(Incubator PMC)</title>
  The committee charged by the <a href=''>board</a>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message