sling-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cziege...@apache.org
Subject svn commit: r1612802 - /sling/site/trunk/content/documentation/development/release-management.mdtext
Date Wed, 23 Jul 2014 09:12:13 GMT
Author: cziegeler
Date: Wed Jul 23 09:12:13 2014
New Revision: 1612802

URL: http://svn.apache.org/r1612802
Log:
CMS commit to sling by cziegeler

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=1612802&r1=1612801&r2=1612802&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/release-management.mdtext (original)
+++ sling/site/trunk/content/documentation/development/release-management.mdtext Wed Jul 23
09:12:13 2014
@@ -177,7 +177,7 @@ If the vote fails, or you decide to redo
 
 If the vote passes:
 
-1. Commit the released artifacts to [https://dist.apache.org/repos/dist/release/sling/][1]
which is replicated to [http://www.apache.org/dist/sling/](http://www.apache.org/dist/sling/)
quickly via svnpubsub. Hint: use svn import to avoid having to checkout the whole folder first.
+1. Commit the released artifacts to [https://dist.apache.org/repos/dist/release/sling/][1]
which is replicated to [http://www.apache.org/dist/sling/](http://www.apache.org/dist/sling/)
quickly via svnpubsub. Hint: use svn import to avoid having to checkout the whole folder first.
The easiest to do this is to get the released artifact using the check script (check_staged_release.sh)
and then simply copy the artifacts from the downloaded folder to your local checkout folder.
Make sure to not add the checksum files for the signature file \*.asc.\*).
 1. Delete the old release artifacts from that same dist.apache.org svn folder (the dist directory
is archived)
 1. Login to [https://repository.apache.org](https://repository.apache.org) with your Apache
SVN credentials. Click on *Staging*. Find your closed staging repository and select it by
checking the select box. Select the *Releases* repository from the drop-down list and click
*Release* from the menu above.
 1. Once the release is promoted click on *Repositories*, select the *Releases* repository
and validate that your artifacts are all there.



Mime
View raw message