incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdelacre...@apache.org
Subject svn commit: r1485989 - /sling/site/trunk/content/documentation/development/release-management.mdtext
Date Fri, 24 May 2013 09:46:58 GMT
Author: bdelacretaz
Date: Fri May 24 09:46:58 2013
New Revision: 1485989

URL: http://svn.apache.org/r1485989
Log:
fix lists formatting

Modified:
    sling/site/trunk/content/documentation/development/release-management.mdtext

Modified: sling/site/trunk/content/documentation/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/release-management.mdtext?rev=1485989&r1=1485988&r2=1485989&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Fri May 24
09:46:58 2013
@@ -1,6 +1,5 @@
 Title: Release Management
 
-
 Sling releases (and SNAPSHOTS) are deployed to the [Nexus repository](http://repository.apache.org)
instead of the traditional deployment via the Maven 2 mirrors source on `people.apache.org`.
This makes the release process much leaner and simpler. In addtion we can benefit from the
Apache Parent POM 6, which has most of the release profile setup built-in.
 
 Most of the hard work of preparing and deploying the release is done by Maven.
@@ -65,29 +64,37 @@ Compare the original `pom.xml` with the 
     [INFO] Retrieving previous build number from apache.snapshots.https
     ...
 
-1. * If you experience an error during deployment like a HTTP 401 check your settings for
the required server entries as outlined in the *Prerequisites*
-1. * Be sure that the generated artifacts respect the Apache release [rules](http://www.apache.org/dev/release.html):
NOTICE and LICENSE files should be present in the META-INF directory within the jar. For \-sources
artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3 which is broken.
The recommended version at this time is 2.0.4
-1. * You should verify the deployment under the [snapshot](https://repository.apache.org/content/groups/snapshots/org/apache/sling)
repository on Apache
-1. Prepare the release
+If you experience an error during deployment like a HTTP 401 check your settings for the
required server entries as outlined in the *Prerequisites*
+
+Make sure the generated artifacts respect the Apache release [rules](http://www.apache.org/dev/release.html):
NOTICE and LICENSE files should be present in the META-INF directory within the jar. For \-sources
artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3 which is broken.
The recommended version at this time is 2.0.4
+
+You should verify the deployment under the [snapshot](https://repository.apache.org/content/groups/snapshots/org/apache/sling)
repository on Apache
+ 
+### Prepare the release
 
     $ mvn release:clean
     $ mvn release:prepare
 
-1. * Preparing the release will create the new tag in SVN, automatically checking in on your
behalf
-1. * If you get a build failure because of an SVN commit problem (namely *The specified baseline
is not the latest baseline, so it may not be checked out.*), just repeat the `mvn release:prepare`
command until SVN is happy. This is based on a known timing issue when using the European
SVN mirror.
-1. Stage the release for a vote
+ Preparing the release will create the new tag in SVN, automatically checking in on your
behalf
+ 
+If you get a build failure because of an SVN commit problem (namely *The specified baseline
is not the latest baseline, so it may not be checked out.*), just repeat the `mvn release:prepare`
command until SVN is happy. This is based on a known timing issue when using the European
SVN mirror.
+
+### Stage the release for a vote
 
     $ mvn release:perform
 
-1. * The release will automatically be inserted into a temporary staging repository for you,
see the Nexus [staging documentation](http://www.sonatype.com/books/nexus-book/reference/staging.html)
for full details
-1. * You can continue to use `mvn release:prepare` and `mvn release:perform` on other sub-projects
as necessary on the same machine and they will be combined in the same staging repository
- this is useful when making a release of multiple Sling modules.
-1. Close the staging repository
-1. * Login to [https://repository.apache.org](https://repository.apache.org) using your Apache
SVN credentials. Click on *Staging* on the left. Then click on *org.apache.sling* in the list
of repositories. In the panel below you should see an open repository that is linked to your
username and IP. Right click on this repository and select *Close*. This will close the repository
from future deployments and make it available for others to view. If you are staging multiple
releases together, skip this step until you have staged everything
-1. Verify the staged artifacts
-1. * If you click on your repository, a tree view will appear below. You can then browse
the contents to ensure the artifacts are as you expect them. Pay particular attention to the
existence of \*.asc (signature) files. If you don't like the content of the repository, right
click your repository and choose *Drop*. You can then rollback your release (see *Canceling
the Release*) and repeat the process
-1. * Note the staging repository URL (especially the number at the end of the URL) you will
need this in your vote email
+The release will automatically be inserted into a temporary staging repository for you, see
the Nexus [staging documentation](http://www.sonatype.com/books/nexus-book/reference/staging.html)
for full details
 
+You can continue to use `mvn release:prepare` and `mvn release:perform` on other sub-projects
as necessary on the same machine and they will be combined in the same staging repository
- this is useful when making a release of multiple Sling modules.
 
+Then, close the staging repository:
+
+  * Login to [https://repository.apache.org](https://repository.apache.org) using your Apache
SVN credentials. Click on *Staging* on the left. Then click on *org.apache.sling* in the list
of repositories. In the panel below you should see an open repository that is linked to your
username and IP. Right click on this repository and select *Close*. This will close the repository
from future deployments and make it available for others to view. If you are staging multiple
releases together, skip this step until you have staged everything
+
+  * Verify the staged artifacts
+    * If you click on your repository, a tree view will appear below. You can then browse
the contents to ensure the artifacts are as you expect them. Pay particular attention to the
existence of \*.asc (signature) files. If you don't like the content of the repository, right
click your repository and choose *Drop*. You can then rollback your release (see *Canceling
the Release*) and repeat the process
+    
+Note the staging repository URL (especially the number at the end of the URL) you will need
this in your vote email
 
 ## Starting the Vote
 



Mime
View raw message