aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1362557 - /aries/site/trunk/content/development/releasingaries.mdtext
Date Tue, 17 Jul 2012 16:17:50 GMT
Author: cumminsh
Date: Tue Jul 17 16:17:50 2012
New Revision: 1362557

Improved formatting


Modified: aries/site/trunk/content/development/releasingaries.mdtext
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Tue Jul 17 16:17:50 2012
@@ -35,7 +35,8 @@ of all Aries modules and their most rece
 ### Choosing a strategy for the release
 Even when releasing a large number of bundles, in Aries we release bundles individually.
If there are dependencies
-between the bundles you want to release, you have three strategies for how to release them.
+between the bundles you want to release, you have four strategies for how to release them.
   * **Release incrementally.** 
     * Release bundles in dependency order, updating dependencies only after releases are
     * This has the advantage that trunk always builds cleanly.
@@ -61,6 +62,8 @@ projects, then close the staging repo an
     * Doing mainline releases from branches plays havoc with git mirroring, so we promised
to try and avoid doing it 
     * See below for extra instructions on releasing from a branch
+In many cases with semantically versioned bundles there won't be dependencies on the latest
and greatest snapshots, which makes everything much easier. 
 ### How to deal with JIRA
 Before actually doing any releasing work through the list of bundles and understand what
defects have been fixed
 (add more about JIRA versions here)

View raw message