Author: rombert
Date: Tue Oct 14 15:51:15 2014
New Revision: 1631801
URL: http://svn.apache.org/r1631801
Log:
Small syntax cleanups
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=1631801&r1=1631800&r2=1631801&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/development/release-management.mdtext
(original)
+++
sling/site/trunk/content/documentation/development/release-management.mdtext
Tue Oct 14 15:51:15 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. 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. Commit the released artifacts to
[https://dist.apache.org/repos/dist/release/sling/](https://dist.apache.org/repos/dist/release/sling/)
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.
@@ -257,8 +257,8 @@ While the Sling IDE tooling is built usi
Once the release has passed, the following must be done:
-1. announce the result of the vote, see [Wait for the
results](#WaitfortheResults)
-1. update versions in jira, see [Update JIRA](#UpdateJIRA)
+1. announce the result of the vote, see [Wait for the
results](#wait-for-the-results)
+1. update versions in jira, see [Update JIRA](#update-jira)
1. upload p2update.zip* to https://dist.apache.org/repos/dist/release/sling/
1. upload unzipped update site to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2
1. upload the source bundle to
https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.2
@@ -364,7 +364,3 @@ To update the OBR you may use the Apache
Wait for the buildbot to update the staging area with your site update
(see dev list for an email).
Then go to the CMS at
[https://cms.apache.org/redirect?uri=http://sling.apache.org/obr](https://cms.apache.org/redirect?uri=http://sling.apache.org/obr)
,
update your checkout and then publish the site.
-
-## Appendix D: Releasing the Sling IDE Tooling
-
-[1]: https://dist.apache.org/repos/dist/release/sling/
