aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1084509 - /aries/site/trunk/content/development/releasingaries.mdtext
Date Wed, 23 Mar 2011 08:48:25 GMT
Author: zoe
Date: Wed Mar 23 08:48:25 2011
New Revision: 1084509

start some doc


Modified: aries/site/trunk/content/development/releasingaries.mdtext
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Wed Mar 23 08:48:25 2011
@@ -1,7 +1,54 @@
 Title: ReleasingAries
 <a name="ReleasingAries-HowtodoanAriesRelease"></a>
-# How to do an Aries Release - Draft release by bundle process
+# How to do an Aries Release
+There are three types of Aries release:
+ 1. Releasing a single Aries bundle (or group of bundles)
+ 1. Releasing a distribution - a group of bundles that work together
+ 1. Releasing the samples
+The outline process is the same in all three cases, further on down this page there are a
lot of details about how the
+Apache release process works and how to get yourself set up to run it, you should read thos
section first if this is 
+your first release. If you are already familiar with the Apache process just use the high
level descriptions in the
+next few paragraphs to perform releases.
+## Releasing a single bundle or group of bundles.
+### What to release? Make a list.
+The Apache release process will not let you release any bundle that has dependencies in -SNAPSHOTS.
If, for example,
+a release of the blueprint API bundle is required the first step is to find and release any
+its dependencies. Because Aries bundles are quite interdependent (see [here](ModuleDependencies)
for an idea
+of how the modules relate to each other, it may be necessary to release quite a large number
of bundles.
+### 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)
+### What version will be released?
+For each bundle on the list check how it's package versions have changed since the last release.
+Based on this, use the versioning policy to determine the version of the bundle that should
be released.
+### Then, for each bundle
+  * mvn release prepare
+  * mvn release perform
+### Complete the process
+Once the bundles are in the staging repository, start a vote on the release. After 72 hours
close the vote. To complete
+the release process it is necessary to copy the new bundles to the dist dir and update table
on the web pages.
+## Releasing a distribution
+## Releasing the samples.
 To create a release you will need to create the release artifacts and move

View raw message