You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@olingo.apache.org by sk...@apache.org on 2013/09/30 16:07:12 UTC
svn commit: r1527574 -
/incubator/olingo/site/trunk/content/doc/release.mdtext
Author: sklevenz
Date: Mon Sep 30 14:07:11 2013
New Revision: 1527574
URL: http://svn.apache.org/r1527574
Log:
CMS commit to olingo by sklevenz
Modified:
incubator/olingo/site/trunk/content/doc/release.mdtext
Modified: incubator/olingo/site/trunk/content/doc/release.mdtext
URL: http://svn.apache.org/viewvc/incubator/olingo/site/trunk/content/doc/release.mdtext?rev=1527574&r1=1527573&r2=1527574&view=diff
==============================================================================
--- incubator/olingo/site/trunk/content/doc/release.mdtext (original)
+++ incubator/olingo/site/trunk/content/doc/release.mdtext Mon Sep 30 14:07:11 2013
@@ -168,26 +168,43 @@ 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>/olingo/<version>
-Once candidate artifacts are available, release manager kicks off the VOTE process.
+Once candidate artifacts are available, release manager kicks off the [VOTE process][3].
If the vote fails, the raised issues will be fixed, a new release candidate will be
built and the VOTE process will be restarted.
If the release candidate gets approved, we can proceed to release publishing.
+### Publishing the Release
+
+If the release candidate gets approved, we can proceed to release publishing:
+
+ - release candidate maven artifacts are promoted in the Apache Maven Repository and
+made available at https://repository.apache.org/content/groups/public/org/apache/olingo/
+ - Maven artifacts are automatically synced to Maven Central at
+http://repo1.maven.org/maven2/org/apache/olingo
+ - release candidate commodity packages are synced (together with their checksum and
+signatures) to http://www.apache.org/dist/olingo
+ - project version at http://chemistry.apache.org/java/opencmis.html is updated
+ - release tag is renamed to final version
+ - release branch is created
+ - Release is closed in Jira
+ - Release is announced to dev@chemistry.apache.org, announce@apache.org
+
### Additional Apache Release Information
- - [Releases Policy][3]
- - [Publishing Releases][4]
- - [Publishing Maven Artifacts][5]
- - [Release Management During Incubation][6]
+ - [Releases Policy][4]
+ - [Publishing Releases][5]
+ - [Publishing Maven Artifacts][6]
+ - [Release Management During Incubation][7]
[1]: http://olingo.incubator.apache.org/documentation.html
[2]: https://issues.apache.org/jira/browse/OLINGO/fixforversion/12324804
- [3]: http://www.apache.org/dev/release.html
- [4]: http://www.apache.org/dev/release-publishing.html
- [5]: http://www.apache.org/dev/publishing-maven-artifacts.html
- [6]: http://incubator.apache.org/guides/releasemanagement.html
+ [3]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote
+ [4]: http://www.apache.org/dev/release.html
+ [5]: http://www.apache.org/dev/release-publishing.html
+ [6]: http://www.apache.org/dev/publishing-maven-artifacts.html
+ [7]: http://incubator.apache.org/guides/releasemanagement.html
\ No newline at end of file