aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cummi...@apache.org
Subject svn commit: r1354221 - in /aries/site/trunk/content/development: devlistvote.txt releasingaries.mdtext verifyingrelease.mdtext
Date Tue, 26 Jun 2012 20:51:58 GMT
Author: cumminsh
Date: Tue Jun 26 20:51:57 2012
New Revision: 1354221

URL: http://svn.apache.org/viewvc?rev=1354221&view=rev
Log:
[ARIES-862] Refinements to release and verification instructions.

Modified:
    aries/site/trunk/content/development/devlistvote.txt
    aries/site/trunk/content/development/releasingaries.mdtext
    aries/site/trunk/content/development/verifyingrelease.mdtext

Modified: aries/site/trunk/content/development/devlistvote.txt
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/devlistvote.txt?rev=1354221&r1=1354220&r2=1354221&view=diff
==============================================================================
--- aries/site/trunk/content/development/devlistvote.txt (original)
+++ aries/site/trunk/content/development/devlistvote.txt Tue Jun 26 20:51:57 2012
@@ -1,56 +1,22 @@
-I've staged a release candidate for Aries 0.2-incubating. The
-following Aries top level modules are staged and tagged in
-https://svn.apache.org/repos/asf/incubator/aries/tags/ 
+I've staged a release candidate for the Aries 1.0.0 test support module. The
+module is staged and tagged in
+https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.testsupport.unit-1.0.0/.
 
-The artifacts are in two staged repos. Links to the *.zip files for each module are provided
below. The source should be built in the order given below because there are dependencies
between some of the modules.
+Instructions for doing a verifying the release are at http://aries.apache.org/development/verifyingrelease.html.
Alternately, cut and paste the following to run a full check:
 
-Modules staged at
-https://repository.apache.org/content/repositories/orgapachearies-113/
-are:
+wget --no-check-certificate https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
+chmod a+x verify_staged_release.sh
+./verify_staged_release.sh 256 mytempdirectory &> verifyresults.txt
+grep FAIL verifyresults.txt
 
-parent 
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/parent/0.2-incubating/parent-0.2-incubating-source-release.zip
 
-eba-maven-plugin
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/eba-maven-plugin/0.2-incubating/eba-maven-plugin-0.2-incubating-source-release.zip
+Artifacts are in one staged repo,
+https://repository.apache.org/content/repositories/orgapachearies-256/.
+Links to the *.zip files for each module are provided below.
 
-testsupport
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/testsupport/testsupport/0.2-incubating/testsupport-0.2-incubating-source-release.zip
+The only module staged is the parent module:
 
-org.apache.aries.util
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/org.apache.aries.util/0.2-incubating/org.apache.aries.util-0.2-incubating-source-release.zip
-
-blueprint
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/blueprint/blueprint/0.2-incubating/blueprint-0.2-incubating-source-release.zip
-
-web
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/web/web/0.2-incubating/web-0.2-incubating-source-release.zip
-
-jmx
-https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/jmx/jmx/0.2-incubating/jmx-0.2-incubating-source-release.zip
-
-
-Modules staged at
-https://repository.apache.org/content/repositories/orgapachearies-129/
-are:
-
-quiesce
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/quiesce/quiesce/0.2-incubating/quiesce-0.2-incubating-source-release.zip
-
-jndi
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/jndi/jndi/0.2-incubating/jndi-0.2-incubating-source-release.zip
-
-transaction
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/transaction/transaction/0.2-incubating/transaction-0.2-incubating-source-release.zip
-
-jpa
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/jpa/jpa/0.2-incubating/jpa-0.2-incubating-source-release.zip
-
-application
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/application/application/0.2-incubating/application-0.2-incubating-source-release.zip
-
-samples
-https://repository.apache.org/content/repositories/orgapachearies-129/org/apache/aries/samples/samples/0.2-incubating/samples-0.2-incubating-source-release.zip
+https://repository.apache.org/content/repositories/orgapachearies-256/org/apache/aries/testsupport/org.apache.aries.testsupport.unit/1.0.0/org.apache.aries.testsupport.unit-1.0.0-source-release.zip
 
 The RAT and IANAL build checks passed. Note that, although RAT is configured to ignore *.MF
and other files that do not require the ASF licence, theses files are still reported incorrectly
as RAT failures.
 
@@ -59,3 +25,4 @@ The vote will be open for 72 hours.
 [ ] +1
 [ ]  0
 [ ] -1
+

Modified: aries/site/trunk/content/development/releasingaries.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/releasingaries.mdtext?rev=1354221&r1=1354220&r2=1354221&view=diff
==============================================================================
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Tue Jun 26 20:51:57 2012
@@ -151,7 +151,7 @@ instructions in the file) and checkin
 Follow the general instructions linked to above. 
 
 <a name="ReleasingAries-Creatingabranchtoreleasefrom"></a>
-### Creating a branch to release from
+### Creating a branch to release from (if needed)
 It is strongly recomended that releases are made from trunk and NEVER from a branch. But,
if you have to release from a branch this is what 
 you will need to do:
 
@@ -282,7 +282,7 @@ For each bundle that needs to be release
 
     Check that there are no depndencies on -SNAPSHOT versions.
     Ensure that everything is committed in SVN
-    mvn release:prepare -Papache-release -DpreparationGoals="clean install" 
+    mvn release:prepare -Papache-release -DpreparationGoals="clean install" -DwaitBeforeTagging="10"
-DscmCommentPrefix="[ARIES-xxx][maven-release-plugin]"
     mvn release:perform -Papache-release
 
 
@@ -291,11 +291,12 @@ For each bundle that needs to be release
 
     1. What is the release version for "Aries :: Top Parent POM"? (org.apache.aries:parent)
0.5: :    
     1. What is SCM release tag or label for "Aries :: Top Parent POM"? (org.apache.aries:parent)
parent-0.5: :
-    1. What is the new development version for "Aries :: Top Parent POM"? (org.apache.aries:parent)
0.6-SNAPSHOT: : 0.5
+    1. What is the new development version for "Aries :: Top Parent POM"? (org.apache.aries:parent)
0.6-SNAPSHOT: : 0.5.1
 
-    i.e. take the default for the first two questions, and set the new development version
to be the same as the one you are releasing! This is because you don't know whether the next
version released from the trunk will have a major, minor or micro version number change -
you won't know until those changes are made! - so leave it for the person making those changes
to make the decision and move to *module*-*new version*-SNAPSHOT.
-
-  * Note 3: mvn release:clean will do *most* of the cleaning up in the event of failures.
+    i.e. take the defaults for the last two questions, but change the release version if
required. You don't know whether the next version released from the trunk will have a major,
minor or micro version number change - you won't know until those changes are made! - but
you have to make a guess. The person doing the next release can make the decision and move
to *module*-*new version*-SNAPSHOT.
+  * Note 3: Since the release plugin makes changes in SCM, use a JIRA for the release (ARIES-XXX
here) in the commit comment to make it easier to see what's changed
+  * Note 4: The task will appear to hang at the end. It's waiting ten seconds to do the tagging,
to ensure everything works in Europe, where svn is mirrored from a US master
+* Note 3: mvn release:clean will do *most* of the cleaning up in the event of failures.
   * Note 4: If on mvn release:prepare you get an error from SVN similar to https://svn.apache.org/repos/asf/!svn/bc/1182408/aries/tags/parent-0.5/default-parent/java5-parent/org.apache.aries.bundle.i.am.releasing
does not exist then it's because there's no scm element in the pom.xml for the module you're
releasing.
  
 
@@ -307,27 +308,6 @@ commands make and commit changes to the 
 create a tag in SVN. To revert the changes you will need to revert the
 pom.xml files and delete the tag from svn.
 
-If you are in Europe the mvn release:prepare command almost always fails at
-the last step, with a message like:
-
-
-    [ERROR]
-     BUILD FAILURE
-    [INFO]
-     ------------------------------------------------------------------------
-    [INFO]
-     Unable to tag SCM
-    Provider message:
-    The svn tag command failed.
-    Command output:
-    svn: No such revision 936951
-
-This is due to the SVN mirroring in place between Europe and the master in
-the US. When you make a commit, it isn't immediately available in Europe to
-svn up to. Just wait 10 secs and repeat the mvn release:prepare command for
-it to restart where it left off.
-
-
 <a name="ReleasingAries-Closingthestagingrepository"></a>
 ##### Closing the staging repository
 After checking that the staging repository contains the artifacts that you
@@ -338,7 +318,7 @@ so that people can check the release.
 ### Running the vote.
 
  At this
-point you should write two notes to the dev@aries.apache.org mailing list.
+point you should write two notes to the dev@aries.apache.org mailing list. You may wish to
ensure they have slightly different subjects, since googlemail seems to ignore anything in
brackets when threading. 
 
  * Subject \[VOTE\]
  Apache Aries release candidate 0N
@@ -386,8 +366,15 @@ the perl script [download_release_artifa
 
 Next, update the Aries Downloads pages to refer to the new artifacts.
 
+### Updating dependencies
+
+Once the release is promoted, change all the bundles which depend on the SNAPSHOT to depend
on the released version. Deployed snapshots get regularly cleaned from the repositories if
there's a released version available, so building against them isn't reliable. 
+
+Don't move bundles which depend on earlier releases to depend on the new release, or they
won't be able to run in an environment with the older bundles. 
+
+
 ### Tidying up tasks
-  * Get the compliance tests run
+  * Get the [compliance tests](http://aries.apache.org/development/compliancetesting.html)
run
   * Release notes
   * Release the component in JIRA (manage components), check the JIRA release notes.
 

Modified: aries/site/trunk/content/development/verifyingrelease.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/verifyingrelease.mdtext?rev=1354221&r1=1354220&r2=1354221&view=diff
==============================================================================
--- aries/site/trunk/content/development/verifyingrelease.mdtext (original)
+++ aries/site/trunk/content/development/verifyingrelease.mdtext Tue Jun 26 20:51:57 2012
@@ -21,6 +21,14 @@ This page provides some help for anyone 
 
 It is essential that the signatures and hashsums are good. Please do read [Verifying Apache
HTTP Server Releases][1] for information on why you should verify releases.. 
 
+These instructions have been rolled up into a script, which you can run instead. Cut and
paste the following:
+
+    wget --no-check-certificate https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh
+    chmod a+x verify_staged_release.sh
+    ./verify_staged_release.sh [RELEASE-NUM] mytempdirectory &> verifyresults.txt
+    grep FAIL verifyresults.txt
+
+
 ##Have I got the KEYS?
 
 To verify Aries release artifacts you need the public keys for the Aries committers.
@@ -58,6 +66,8 @@ Ensure the checksums are right for the r
         fi
     done
 
+(On the Mac, use `md5 -q` instead of `md5sum` and the cut.)
+
 Do something similar for sha1:
 
     for i in `find content -type f | egrep -v '.md5$|.sha1$|index.html|maven-metadata.xml'`
@@ -72,6 +82,8 @@ Do something similar for sha1:
         fi
     done
 
+(On the Mac, use `openssl sha1` instead of `sha1sum`.)
+
 Ensure the PGP signature files are good. See the [Validating section of Verifying Apache
HTTP Server Releases][2] for background on validating the authenticity of a key.
 
     for i in `find content -type f | egrep '.asc$'`
@@ -97,9 +109,11 @@ It's also a good idea to run the [Apache
 
     mvn -fn -Prat
 
-Note: currently RAT fails due to the generated DEPENDENCIES file not containing a license.
It's safe to ignore this as the file is generated. So in order to ensure RAT checks all subdirectories,
use the -fn.
+Note: currently RAT fails due to the generated DEPENDENCIES file not containing a license.
It's safe to ignore this as the file is generated. So in order to ensure RAT checks all subdirectories,
use the -fn. Then check any failures with
+   
+    find . -name \*.rat | xargs grep \!\?\?
 
 
   [1]: http://httpd.apache.org/dev/verification.html
   [2]: http://httpd.apache.org/dev/verification.html#Validating
-  [3]: http://incubator.apache.org/rat/
\ No newline at end of file
+  [3]: http://incubator.apache.org/rat/



Mime
View raw message