Author: dklco
Date: Wed May 29 14:05:44 2013
New Revision: 1487493
URL: http://svn.apache.org/r1487493
Log:
Cleaning up some more issues in the appendices
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=1487493&r1=1487492&r2=1487493&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/development/release-management.mdtext
(original)
+++
sling/site/trunk/content/documentation/development/release-management.mdtext
Wed May 29 14:05:44 2013
@@ -242,36 +242,31 @@ Also create a new version X.Y.Z+2, if th
*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
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)
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:
-1. *Create a public/private pair key*:
+1. Create a public/private pair key:
- $ gpg --gen-key
+ $ gpg --gen-key
-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).
+ 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"
- $ (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"
+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. 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
-
-You also have to add your public key either on pool.sks-keyservers.net or
pgp.mit.edu (for the statging repository).
+ $ (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"
+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
+ You also have to add your public key either on pool.sks-keyservers.net or
pgp.mit.edu (for the statging repository).
## Appendix B: preparing releases on Mac OS X
@@ -289,11 +284,11 @@ When running the `mvn release:prepare` c
svn: Commit failed (details follow):
svn: MKACTIVITY of
'/repos/asf/!svn/act/4f11ad5d-9161-0410-b4dd-cb727141ea8c': authorization
failed (https://svn.apache.org){code}
-This is due to a bug in Subversion on the Mac, as described by Brett Porter in
his
[blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/].
He proposes putting an "svn" script at the head of your path to fix the issue.
+This is due to a bug in Subversion on the Mac, as described by Brett Porter in
his
[blog](http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/).
He proposes putting an "svn" script at the head of your path to fix the issue.
## Appendix C: Deploy bundles on the Sling OBR
-We are mainting an OSGi Bundle Repository providing all release of the Sling
Bundles. This repository is maintained as part of the Apache Sling site and is
available at [http://sling.apache.org/obr/sling.xml]. The source for this page
is maintained in the SVN repository below the _site_, that is at
[http://svn.apache.org/repos/asf/sling/site/]. To update the Sling OBR
repository you must be an Apache Sling Committer since this requires SVN write
access.
+We are mainting an OSGi Bundle Repository providing all release of the Sling
Bundles. This repository is maintained as part of the Apache Sling site and is
available at
[http://sling.apache.org/obr/sling.xml](http://sling.apache.org/obr/sling.xml).
The source for this page is maintained in the SVN repository below the _site_,
that is at
[http://svn.apache.org/repos/asf/sling/site/](http://svn.apache.org/repos/asf/sling/site/).
To update the Sling OBR repository you must be an Apache Sling Committer since
this requires SVN write access.
To update the OBR you may use the Apache Felix Maven Bundle Plugin which
prepares the bundle descriptor to be added to the OBR file. Follow these steps
to update the OBR:
@@ -336,12 +331,12 @@ To update the OBR you may use the Apache
$ svn commit -m"Add Bundle ABC Version X.Y.Z" obr/sling.xml
-4. Update the Site on [people.apache.org]{people.apache.org}
+4. Update the Site on [people.apache.org](people.apache.org)
-After committing the changes, you have to update the site source, which is
getting mirrored to the web servers on [people.apache.org]{people.apache.org}
+ After committing the changes, you have to update the site source, which is
getting mirrored to the web servers on [people.apache.org](people.apache.org)
- $ ssh people.apache.org svn update /x1/www/sling.apache.org/obr/sling.xml
+ $ ssh people.apache.org svn update
/x1/www/sling.apache.org/obr/sling.xml
-After updating the site source it will generally take an hour or two until the
changes are visible on the web.
+ After updating the site source it will generally take an hour or two until
the changes are visible on the web.
[1]: https://dist.apache.org/repos/dist/release/sling/
\ No newline at end of file
