incubator-sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dk...@apache.org
Subject svn commit: r1500727 - /sling/site/trunk/content/documentation/development/release-management.mdtext
Date Mon, 08 Jul 2013 13:50:56 GMT
Author: dklco
Date: Mon Jul  8 13:50:56 2013
New Revision: 1500727

URL: http://svn.apache.org/r1500727
Log:
Updated the release management page to reflect the latezt information on the GPG keys from
the infrastructure team.  Also fixed some minor issues

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=1500727&r1=1500726&r2=1500727&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Mon Jul 
8 13:50:56 2013
@@ -12,7 +12,7 @@ Most of the hard work of preparing and d
 ## Prerequisites
 
 * To prepare or perform a release you *MUST BE* at least be an Apache Sling Committer.
-* Each and every release must be signed; therefore the public key should be cross signed
by other Apache committers (not required but suggested) and this public key should be added
to [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS) and either
on pool.sks-keyservers.net or pgp.mit.edu (See Appendix A)
+* Each and every release must be signed; therefore the public key should be cross signed
by other Apache committers (not required but suggested) and this public key should be added
to [https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
and either on pool.sks-keyservers.net or pgp.mit.edu (See Appendix A)
 * When preparing the release on Mac OS X, check out Appendix B before trying the steps in
the next chapter.
 * Make sure you have all Apache servers defined in your [settings.xml](http://maven.apache.org/developers/committer-settings.html)
 
@@ -130,9 +130,6 @@ Propose a vote on the dev list with the 
     
     This vote will be open for 72 hours.
 
-
-
-
 ## Wait for the Results
 
 From [Votes on Package Releases](http://www.apache.org/foundation/voting.html):
@@ -182,8 +179,6 @@ If the vote fails, or you decide to redo
 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 a closed repository that is linked to your
username and IP (if it's not yet closed you need to right click and select *Close*). Right
click on this repository and select *Drop*.
 1. Rollback the version in the `pom.xml` and commit any fixes you need to make
 
-
-
 ## Promoting the Release
 
 If the vote passes:
@@ -198,19 +193,14 @@ If the vote passes:
 
 For the last two tasks, it's better to give the mirrors some time to distribute the uploaded
artifacts (one day should be fine). This ensures that once the website (news and download
page) is updated, people can actually download the artifacts.
 
-
-
 ## Update JIRA
 
 Go to [Manage Versions](https://issues.apache.org/jira/plugins/servlet/project-config/SLING/versions)
section on the SLING JIRA and mark the X.Y.Z version as released setting the release date
to the date the vote has been closed.
 
 Also create a new version X.Y.Z+2, if that hasn't already been done.
 
-
-
 ## Create an Announcement
 
-
     To: "Sling Developers List" <dev@sling.apache.org>, "Apache Announcements" <announce@apache.org>
     Subject: [ANN] Apache Sling ABC version X.Y.Z Released
     
@@ -229,8 +219,7 @@ Also create a new version X.Y.Z+2, if th
         <artifactId>org.apache.sling.ABC</artifactId>
         <version>X.Y.Z</version>
     </dependency>
-    
-    
+        
     Release Notes:
     
     <<insert release notes in text format from JIRA>>
@@ -239,8 +228,6 @@ Also create a new version X.Y.Z+2, if th
     
     -The Sling team
 
-
-
 *Important*: Add the release to the Software section of the next board report below [Reports](https://cwiki.apache.org/confluence/display/SLING/Reports).
 
 ## Related Links
@@ -248,7 +235,7 @@ Also create a new version X.Y.Z+2, if th
 1. [http://www.apache.org/dev/release-signing.html](http://www.apache.org/dev/release-signing.html)
 1. [http://wiki.apache.org/incubator/SigningReleases](http://wiki.apache.org/incubator/SigningReleases)
 
-## Appendix A: Create and Add your key to [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS)
+## Appendix A: Create and Add your key to [https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
 
 Considering that you are using a \*nix system with a working OpenSSH, GnuPG, and bash you
can create and add your own key with the following command:
 
@@ -259,13 +246,12 @@ Considering that you are using a \*nix s
     When gpg asks for e-mail linked the key you *MUST USE* the <committer>@apache.org
one
     When gpg asks for comment linked the key you *SHOULD USE* "CODE SIGNING KEY"
 
-1. Add the key to [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS)
type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).
+1. Add the key to [https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).
 
-        $ (gpg --list-sigs e-mail && gpg --export --armor e-mail) > toadd.key
-        $ scp toadd.key people.apache.org:
-        $ ssh people.apache.org "cat toadd.key >> /x1/www/www.apache.org/dist/sling/KEYS"
+        $ gpg --fingerprint <committer>@apache.org
 
-1. You are *DONE*, but to see the changes on [http://www.apache.org/dist/sling/KEYS](http://www.apache.org/dist/sling/KEYS)
you must wait 2 hours
+1. Add the key signature into the field 'OpenPGP Public Key Primary Fingerprint' in your
profile at [https://id.apache.org](https://id.apache.org)
+1. You are *DONE*, but to see the changes on [https://people.apache.org/keys/group/sling.asc](https://people.apache.org/keys/group/sling.asc)
you may need to wait a few hours
 
     You also have to add your public key either on pool.sks-keyservers.net or pgp.mit.edu
(for the statging repository).
 
@@ -316,15 +302,15 @@ To update the OBR you may use the Apache
     
     Instead of checking out and building the project locally, you may also use the `deploy-file`
goal of the Maven Bundle Plugin:
 
-        $ wget http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.jar
-        $ wget http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.pom
+        $ wget http://repo1.maven.org/maven2/org/apache/sling/the\_module/version/the\_module-version.jar
+        $ wget http://repo1.maven.org/maven2/org/apache/sling/the\_moduleversion/the\_module-version.pom
         $ mvn org.apache.felix:maven-bundle-plugin:deploy-file \
-            -Dfile=the*module-version.jar -DpomFile=the*module-version.pom \
-            -DbundleUrl=http://repo1.maven.org/maven2/org/apache/sling/the*module/version/the*module-version.jar
\
+            -Dfile=the\_module-version.jar -DpomFile=the\_module-version.pom \
+            -DbundleUrl=http://repo1.maven.org/maven2/org/apache/sling/the\_module/version/the\_module-version.jar
\
             -Durl=file:///path_to_site_checkout/obr \
             -DprefixUrl=http://repo1.maven.org/maven2 \
             -DremoteOBR=sling.xml
-        $ rm the*module-version.jar the*module-version.pom
+        $ rm the\_module-version.jar the*module-version.pom
 
 3. Commite the Site Changes
 



Mime
View raw message