svn commit: r1662389 - in /felix/sandbox/pderop/dependencymanager/release: README README.release

[pd...@apache.org]

Author: pderop
Date: Thu Feb 26 09:02:50 2015
New Revision: 1662389

URL: http://svn.apache.org/r1662389
Log:
Renamed to release/README to release/README.release. the release name is now org.apache.felix.dependency-r<n> instead of apache-felix-dependencymanager-r<n> (in order to be consistent with other felix sub projects).

Added:
    felix/sandbox/pderop/dependencymanager/release/README.release
      - copied, changed from r1662323, felix/sandbox/pderop/dependencymanager/release/README
Removed:
    felix/sandbox/pderop/dependencymanager/release/README

Copied: felix/sandbox/pderop/dependencymanager/release/README.release (from r1662323, felix/sandbox/pderop/dependencymanager/release/README)
URL: http://svn.apache.org/viewvc/felix/sandbox/pderop/dependencymanager/release/README.release?p2=felix/sandbox/pderop/dependencymanager/release/README.release&p1=felix/sandbox/pderop/dependencymanager/release/README&r1=1662323&r2=1662389&rev=1662389&view=diff
==============================================================================
--- felix/sandbox/pderop/dependencymanager/release/README (original)
+++ felix/sandbox/pderop/dependencymanager/release/README.release Thu Feb 26 09:02:50 2015
@@ -18,27 +18,28 @@ Before you can start staging a release c
 * make sure there are no dependencies on snapshots/unreleased versions;
 * create a tagged version of the sources in preparation of the release candidate.
 
-Creating a tagged version of the sources can be done directly through svn:
+Creating a tagged version of the sources can be done directly through svn (replace r<n> by the actual release number, like "r1"):
 
-svn copy https://svn.apache.org/repos/asf/felix/trunk/dependencymanager https://svn.apache.org/repos/asf/felix/releases/dependencymanager-X.Y.Z -m "Release of Apache Felix Dependency Manager X.Y.Z"
+svn copy https://svn.apache.org/repos/asf/felix/trunk/dependencymanager https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.dependencymanager-r<n> -m "Release of Apache Felix Dependency Manager r<n>"
 
 Staging a release candidate
 ===========================
 
-Staging a release starts by checking out a tagged version of the sources:
+Staging a release starts by checking out a tagged version of the sources (replace r<n> by the actual release number, like "r1"):
 
-svn co https://svn.apache.org/repos/asf/felix/releases/dependencymanager.X.Y.Z dependencymanager-X.Y.Z
+svn co https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.dependencymanager-r<n>
 
 The next step is to build/test the software and create the release/staging/ directory (where the source/jars will be packaged):
+(replace r<n> by the actual release number, like "r1")
 
-$ cd dependencymanager-X.Y.Z/
+$ cd org.apache.felix.dependencymanager-r<n>
 $ ./gradlew rat 
 $ ./gradlew org.apache.felix.dependencymanager.annotation:jar
 $ ./gradlew jar
 $ ./gradlew test
 $ ./gradlew check
 
-Then Edit the ./release/build.gradle script, and modify the "dmVersion", and create the staging:
+Then Edit the ./release/build.gradle script, increment the "ext.dmRelease" property, and create the staging:
 
 $ ./gradlew makeStaging (this will create ./release/staging/ directory)
 
@@ -46,39 +47,61 @@ Then you sign archives by invoking the f
 
 $ ./gradlew signStaging
 
-you can upload the archives and the signatures to our development area, which we use to stage this release candidate. This development area can be found at 
+You can upload the archives and the signatures to our development area, which we use to stage this release candidate. This development area can be found at 
 https://dist.apache.org/repos/dist/dev/felix and adding files to it can be done using "svnpubsub" which is taken care of by the following target:
 
-$ ./gradlew commitToStaging -PsvnUser=youSvnUser -PsvnPassword=yourSvnPassword
+$ ./gradlew commitToStaging
 
 Voting on the release
 =====================
 
-Start a vote on the dev@felix.apache.org list, for example (be sure to replace X.Y.Z with the correct version!):
+Start a vote on the dev@felix.apache.org list, for example (be sure to replace r<n> with the correct release number, like "r1"):
 
-The staging version can be checked using the following script:
+>>>
+To: "Felix Developers List" <de...@felix.apache.org>
+Subject: [VOTE] Release of Apache Felix Dependency Manager release r<n>
 
-  http://svn.apache.org/viewvc/felix/trunk/dependencymanager/release/check_staged_release.sh
+Hi,
 
-Usage:
+We solved N issues in this release:
+http://issues.apache.org/jira/...
+
+There are still some outstanding issues:
+http://issues.apache.org/jira/...
+
+Staging repository:
+https://dist.apache.org/repos/dist/dev/felix/apache-felix-dependencymanager-r<n>/
 
-$ sh check_staged_release.sh X.Y.Z
+You can use this UNIX script to download the release and verify the signatures:
+http://svn.apache.org/repos/asf/felix/trunk/dependencymanager/release/check_staged_release.sh
+
+Usage:
+sh check_staged_release.sh r<n> /tmp/felix-staging
 
 This script, unlike the original Felix check_stage_release.sh, will download staging from https://dist.apache.org/repos/dist/dev/felix instead of 
 http://repository.apache.org/content/repositories.
 
+
+Please vote to approve this release:
+
+[ ] +1 Approve the release
+[ ] -1 Veto the release (please provide specific comments)
+
+This vote will be open for 72 hours.
+<<<
+
 Promoting the release:
 =====================
 
 Move the artifacts from the development area to the final release location at 
 https://dist.apache.org/repos/dist/release/felix by invoking the following target:
 
-$ ./gradlew promoteToRelease -PsvnUser=youSvnUser -PsvnPassword=yourSvnPassword
+$ ./gradlew promoteToRelease
 
 Cancelling the release
 ======================
 
-$ ./gradlew deleteFromStaging -PsvnUser=youSvnUser -PsvnPassword=yourSvnPassword
+$ ./gradlew deleteFromStaging
 
 [1] http://www.apache.org/dev/release.html
 [2] http://www.apache.org/dist/felix/KEYS