Author: psharples
Date: Wed Feb 13 13:44:55 2013
New Revision: 1445593
URL: http://svn.apache.org/r1445593
Log:
Updated release instructions incorporating new svn/pub sub info.
Modified:
wookie/site/trunk/content/docs/developer/release-process.mdtext
Modified: wookie/site/trunk/content/docs/developer/release-process.mdtext
URL:
http://svn.apache.org/viewvc/wookie/site/trunk/content/docs/developer/release-process.mdtext?rev=1445593&r1=1445592&r2=1445593&view=diff
==============================================================================
--- wookie/site/trunk/content/docs/developer/release-process.mdtext (original)
+++ wookie/site/trunk/content/docs/developer/release-process.mdtext Wed Feb 13
13:44:55 2013
@@ -166,9 +166,10 @@ Ideally we'd want a +3 from the committe
1. If you haven't already, switch back to the trunk.
1. Find all the files listed in step (#5.1) above.
- 1. Update all the entries to the next version-SNAPSHOT - i.e. 0.13.0-SNAPSHOT
+ 1. Update all the entries to the next (minor) version-SNAPSHOT - i.e.
0.12.1-SNAPSHOT
1. Update the 3 pom-template.xml files in step (#5.2) above so that they
point back at the trunk again
1. Commit your changes
+ 1. Once a release candidate has been successfully voted and released, it is
recommended to repeat the steps here (8) but roll the version nmuber to the
next version proper (e.g. from 0.12.1 to 0.13.0)
### 9. Inform commiters that you have finished
@@ -213,20 +214,20 @@ Ideally we'd want a +3 from the committe
- the standalone builds will run when you click it's startup script (May
need to add executable permissions on mac/linux)
- examine the WAR build for integrity (also ideally drop the WAR file into
a preconfigured tomcat/mysql instance on your machine to make sure it
deploys/works okay)
-### 11. Upload the artifacts to people.apache.org
+### 11. Upload the artifacts to https://dist.apache.org/repos/dist/dev/wookie/
- 1. Make sure you delete the 3 rat-report.txt files (otherwise the next stage
will upload them)
- 1. From the 'wookie/release' folder run the following to upload the
generated build folder and artifacts...
-
- scp -r ${project.version}
${user.name}@people.apache.org:/www/people.apache.org/builds/wookie/
-
- ...substituting the ${project.version} with the folder name of the
generated artifacts i.e...
+Since Wookie became a TLP we have moved away from the old method of publishing
release candidates to people.apache.org. We now use the
+[https://dist.apache.org/repos/dist/dev/wookie/](https://dist.apache.org/repos/dist/dev/wookie/)
subversion area to manage these.
+Releases once successfully voted on are moved to the
+[https://dist.apache.org/repos/dist/release/wookie/](https://dist.apache.org/repos/dist/release/wookie/)
area.
+See [here](http://www.apache.org/dev/release#upload-ci) for more information.
- scp -r ./0.12.0
[email protected]:/www/people.apache.org/builds/wookie/
-
- (Note: the pscp utility comes with putty, rather than scp)
-
- 1. Verify they are downloadable from http://people.apache.org/builds/wookie
+ 1. Make sure you delete the 3 rat-report.txt files (otherwise the next stage
will upload them)
+ 1. From the 'wookie/release' folder copy the ${project.version} folder to
your eclipse project which points to the RC subversion area
(https://dist.apache.org/repos/dist/dev/wookie/)
+ 1. Check and make sure that all the binaries are present and that there are
no extra resources, other than what was generated by the build script in (10)
(No unzipped tar.gz files for example)
+ 1. Commit the new binaries to svn.
+ - (You can alternatively use the svn command line tool, rather than
eclipse if you wish)
+ 1. Verify they are downloadable from
https://dist.apache.org/repos/dist/dev/wookie/
### 12. Upload the Nexus release artifacts
@@ -281,20 +282,17 @@ Ideally we'd want a +3 from the committe
- https://repository.apache.org/index.html
- Staging repositories (under Build Promotion) --> Name column -->
org.apache.wookie
- click checkbox of the closed staging repo (org.apache.wookie-***) and
select Release.
- 1. Copy the release artifacts over to the distribution area
- - login to people.apache.org and copy across the build folder
+ 1. Move the release artifacts over to the distribution area
+ - (Author note - I cant find a way to do this in eclipse so use the
command line tool instead)
+ - The artifacts need to be moved from the RC area to the RELEASES area.
Open a command prompt and use...
+
+ svn move -m "Apache Wookie ${project.version} RELEASE"
https://dist.apache.org/repos/dist/dev/wookie/${project.version}
https://dist.apache.org/repos/dist/release/wookie/
- cp -r /www/people.apache.org/builds/wookie/${project.version}
/www/www.apache.org/dist/wookie
-
(replacing the version name accordingly)
+
+ (Note: You will be prompted for a Password. If the username is not your
apache userid, you might have to press enter once so that you are prompted for
your apache username, rather than your local one)
- verify the folder and contents copied across okay.
- 1. Delete the staged version (cleanup)
- - login to people.apache.org (if not already) and delete the old staged
release
-
- rm -rfv /www/people.apache.org/builds/wookie/${project.version}
-
- (replacing the version name accordingly)
1. Update the staged website
- Update the downloads page and source page to add new version using the
mirrored URLs
@@ -329,9 +327,9 @@ Ideally we'd want a +3 from the committe
$ svn del
https://svn.apache.org/repos/asf/wookie/tags/${project.version} -m "deleting
tag from rolled back release"
- 1. Delete the build artifacts on people
+ 1. Delete the build artifacts in the RC area
- $ rm -rfv /www/people.apache.org/builds/wookie/${project.version}
+ $ svn del
https://dist.apache.org/repos/dist/dev/wookie/${project.version} -m "deleting
release candidate from rolled back release"
1. Drop the nexus staging repo
- https://repository.apache.org/index.html
