incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mar...@apache.org
Subject svn commit: r1369715 - /incubator/public/trunk/content/guides/releasemanagement.xml
Date Mon, 06 Aug 2012 02:54:47 GMT
Author: marvin
Date: Mon Aug  6 02:54:46 2012
New Revision: 1369715

URL: http://svn.apache.org/viewvc?rev=1369715&view=rev
Log:
Generalize a few language-specific passages.

Modified:
    incubator/public/trunk/content/guides/releasemanagement.xml

Modified: incubator/public/trunk/content/guides/releasemanagement.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/releasemanagement.xml?rev=1369715&r1=1369714&r2=1369715&view=diff
==============================================================================
--- incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] Mon Aug  6 02:54:46
2012
@@ -931,7 +931,7 @@ Incubating projects should ensure that e
 Collecting all this information may seem a little daunting especially for a starting project.
 Not at all agile. One approach may be to ask developers to update documentation
 as they make changes. 
-Another is to use a to (for example maven) to collect this information automatically.
+Another is to use a build tool to collect this information automatically.
 A third is for the release manager to collect all the information required
 when the release is made. The disadvantage of this method is that increases
 the work required to create a release.
@@ -946,7 +946,7 @@ with each release as adoption grows.
         	<p>
  RELEASE_NOTES (TODO:link). Remember to include a description of the project.
  CHANGES (link) these may be contained in a separate document
- (TODO: maven) or included in the RELEASE NOTES. svn log can be used to collect changes.
+ or included in the RELEASE NOTES. svn log can be used to collect changes.
   This is a good opportunity to reinforce the need for good commit messages.
  CHANGES should also include references to bugs fixed (TODO URLS, searches in JIRA or bugzilla).
  Include a description of the build process either in a README or BUILDING document.
@@ -1192,9 +1192,9 @@ on new features, freshmeat, downstream p
         <section id='best-practice-dependencies'><title>Dependencies</title>
         	<p>
 As well as libraries, projects often have more subtle dependencies.
-Many languages (for example Java and Perl) have different versions.
-It is important that the versions of a language upon which a project
-will run are clearly documented. The <a href='TODO:'>release notes</a>
+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. 
         	</p>
@@ -2129,7 +2129,8 @@ manager should tally the votes and decla
 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
-maven central if appropriate, and announcing the release to the public.
+downstream distribution channels if appropriate, and announcing the release to
+the public.
                 </p>
             <p>
             TODO (include link to infra documentation)



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


Mime
View raw message