svn commit: r1610360 - /olingo/site/trunk/content/doc/release.mdtext

[mi...@apache.org]

Author: mibo
Date: Mon Jul 14 08:50:52 2014
New Revision: 1610360

URL: http://svn.apache.org/r1610360
Log:
Updated release guide

Modified:
    olingo/site/trunk/content/doc/release.mdtext

Modified: olingo/site/trunk/content/doc/release.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/release.mdtext?rev=1610360&r1=1610359&r2=1610360&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/release.mdtext (original)
+++ olingo/site/trunk/content/doc/release.mdtext Mon Jul 14 08:50:52 2014
@@ -173,7 +173,7 @@ The release candidate artifacts:
   - Maven artifacts will be staged on repository.apache.org. A new staging repo 
 is created per RC and will be communicated upon release.
   - Distribution commodity packages are staged at 
-http:/people.apache.org/~<username>/olingo/<version> 
+http://people.apache.org/~[username]/olingo2/[version] (e.g. http://people.apache.org/~mibo/olingo2/2.0.0-RC01)
 
 Once candidate artifacts are available, release manager kicks off the [VOTE process][3].
 
@@ -186,7 +186,7 @@ If the release candidate gets approved, 
 
 This checklist helps verifying if a release candidate is valid:
 
-* Are all files on http:/people.apache.org/~<username>/olingo/<version> ?
+* Are all files on "http://people.apache.org/~[username]/olingo2/[version]"?
 * Check if md5, sha512 and asc files are filled correctly?
 * Can the zip files be unpacked without issues?
 * Execute a "mvn clean install -Pbuild.quality" on parent distribution. It should work without issues.
@@ -205,7 +205,10 @@ If the release candidate gets approved, 
 
   - Release candidate maven artifacts are promoted in the Apache Maven Repository and 
 made available [here](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo~~~~).
-  - Maven artifacts are automatically synced to [Maven Central](http://search.maven.org/#search|ga|1|org.apache.olingo).
+  - Publish final release Version to [Apache Repository](https://repository.apache.org/)
+    - First publish via `mvn deploy -Papache.release` into the *Staging Area*
+    - From *Staging Area* close and release the staged Artifacts to finish publishing 
+    - Afterwards the Maven artifacts are automatically synced to [Maven Central](http://search.maven.org/#search|ga|1|org.apache.olingo).
   - Release candidate commodity packages are synced (together with their checksum and 
 signatures) to [Apache Distributions](http://www.apache.org/dist/olingo/).
   - Release tag is renamed to final version.