[onebusaway] r5505 committed - Edited wiki page ReleaseManagement through web user interface.

[onebu...@googlecode.com]

Revision: 5505
Author: bdfe...@onebusaway.org
Date: Sun Feb 19 09:22:06 2012
Log: Edited wiki page ReleaseManagement through web user interface.
http://code.google.com/p/onebusaway/source/detail?r=5505

Modified:
/wiki/ReleaseManagement.wiki

=======================================
--- /wiki/ReleaseManagement.wiki Sun Aug 28 16:39:34 2011
+++ /wiki/ReleaseManagement.wiki Sun Feb 19 09:22:06 2012
@@ -1,102 +1,2 @@
-#summary Details for OBA project managers on performing a release
-
-= Introduction =
-
-The !OneBusAway project is composed of a number of Maven [Modules
modules]. Every once in a while, when the stars and the patches align, a
module is deemed ready for an official release. This page attempts to
document everything you'll need to perform an official release of
a !OneBusAway module. Typically, this information will only be useful to a
handful of core !OneBusAway project managers.
-
-The typical Maven release process looks like:
-
-{{{
-mvn release:prepare
-mvn release:perform
-}}}
-
-and it's pretty much the same for !OneBusAway. The trick is making sure
you have all the proper permissions and credentials to perform the release.
-
-= Before You Release =
-
-== Commit Privileges ==
-
-You'll need commit privileges on the !OneBusAway SVN repository.
-
-== Configure your ~/.m2/settings.xml File ==
-
-You'll need a couple of entries in your `~/.m2/settings.xml` Maven
settings file.
-
-{{{
-<profiles>
- <profile>
- <id>onebusaway-release</id>
- <properties>
- <gpg.passphrase>########</gpg.passphrase>
- </properties>
- </profile>
- <profile>
- <id>oba-distribution</id>
- <properties>
- <distribution_id>nexus.onebusaway.org-releases</distribution_id>
-
<distribution_url>http://nexus.onebusaway.org/content/repositories/releases/</distribution_url>
-
<snapshot_distribution_id>nexus.onebusaway.org-snapshots</snapshot_distribution_id>
-
<snapshot_distribution_url>http://nexus.onebusaway.org/content/repositories/snapshots/</snapshot_distribution_url>
- </properties>
- </profile>
-</profiles>
-
-<servers>
- <server>
- <id>sonatype-nexus-staging</id>
- <username>contact_onebusaway</username>
- <password>########</password>
- </server>
- <server>
- <id>nexus.onebusaway.org-releases</id>
- <username>deployment</username>
- <password>########</password>
- </server>
- <server>
- <id>developer.onebusaway.org</id>
- <username>onebus</username>
- <privateKey>path/to/id_rsa</privateKey>
- </server>
-</servers>
-}}}
-
-This does a couple of things:
- * Specifies your GPG passphrase to use when signing releases (more on
that later)
- * Specifies that when the `oba-distribution` profile is active, we
change the distribution points to be the [http://nexus.onebusaway.org/
OneBusAway Maven repository] (it's https://oss.sonatype.org/ by default).
- * Specifies the username and password for deployment to the
https://oss.sonatype.org/ Nexus staging repository.
- * Specifies the username and password for the
[http://nexus.onebusaway.org/ OneBusAway Maven repository]
- * Specifies the username and ssh private key for accessing the
http://developer.onebusaway.org/ server for deploying site documentation.
-
-== GPG Key ==
-
-We sign our Maven releases with a GPG key so that others can verify that
they really came from us. You'll need both the !OneBusAway public and
private key. Once you have them, you import them into your GPG keystore
with the following commands:
-
-{{{
-gpg --import public.key
-gpg --allow-secret-key-import --import private.key
-}}}
-
-If you ever need to export the keys:
-
-{{{
-gpg --export -a "OneBusAway Contact" > public.key
-gpg --export-secret-key -a "OneBusAway Contact" > public.key
-}}}
-
-= Project Configuration =
-
-Typically, when working with an existing project, most of the project
configuration will have already been taken care of.
-
-= Perform a Release =
-
-Now that you've got everything ready to go, it's time to perform a release.
-
-{{{
-mvn release:prepare
-mvn release:perform
-cd target/checkout
-mvn -P oba-distribution javadoc:jar source:jar deploy site-deploy
-}}}
-
-Note that the standard `release:prepare` and `release:perform` steps are
included, but we have one additional step. Once the Maven release has been
performed, we additionally want to make sure that all release artifacts
have been deployed to the OneBusAway repository and that the documentation
has been deployed to the http://developer.onebusaway.org/
+#labels Deprecated
+Moved to https://github.com/OneBusAway/onebusaway/wiki/Release-Management