Graham/Lawrence,
I have documented the steps for Woden release mgt. Probably needs to be in 
a web or wiki page, but this was the quick option for now.

Use the branch 'M7b' in Woden SVN for the Woden M7b release. I have 
already updated the release notes in release-notes.html.

Any software release published by an incubator project must be approved by 
the Incubator PMC, so you need to follow this process right through to 
Incubator PMC approval (i.e. the Axis2 release can only include 
IPMC-approved Woden code). 

Note, Axiom 1.2.5 and XmlSchema 1.3.2 need to be released before starting 
the Woden vote (their binary jar files are included in the Woden binary 
distro and it's these Woden archives that the IPMC will vote on). Update 
build.properties with the new jar files names.

When posting a vote request to any mailing list, start the subject line 
with the eye-catcher [VOTE].
Likewise when posting vote results or release announcements.... [RESULT] 
or [ANNOUNCE].
See the links below for examples of these mailing list postings.

Release management steps:
=====================

1) Build and test Woden M7b. The 'buildDist' ANT target will create the 
binary and source archives  (.zip, .tar.gz, .tar.bz2) and the hash digests 
(md5, sha1) for each archive file.

2) Sign the binary and source archives, which will create a .asc signature 
file for each archive file.
e.g.
gpg --armor --output apache-woden-incubating-1.0M7a.zip.asc --detach-sig 
apache-woden-incubating-1.0M7a.zip
gpg --verify apache-woden-incubating-1.0M7a.zip.asc 
apache-woden-incubating-1.0M7a.zip

3) Upload the binary and source archives and their hash digests and 
signature files to people.apache.org into some directory path under your 
public_html directory so that you can include a link to the files in the 
[VOTE] request email. 
Also upload the KEYS file and release-notes.html from [woden root] and 
junit-noframes.html from the [woden root]/build/test-results/html 
directory.
Make sure you chmod the file permissions so others can read them (e.g. 
744).

E.g. 
[jkaputin home]/public_html/woden/milestones/1.0M7a-incubating
...is accessible at url...
http://people.apache.org/~jkaputin/woden/milestones/1.0M7a-incubating/

Note, because Woden is in incubation you must not upload these files to 
the Woden project on the file server until the Incubator PMC vote has 
passed....so you upload to your own space, then move to Woden space after 
voting.

4) Check that you can download/unzip the files. 
Create hash digests of the downloaded archives and check them against the 
downloaded hash files.
e.g.
$ dir
apache-woden-incubating-1.0M7a.zip  apache-woden-incubating-1.0M7a.zip.MD5
$ cat apache-woden-incubating-1.0M7a.zip.MD5
3009d6f6fea14b7536c22028944bb03a
$ md5sum apache-woden-incubating-1.0M7a.zip
3009d6f6fea14b7536c22028944bb03a *apache-woden-incubating-1.0M7a.zip

5) Post a vote request email to woden-dev asking devs to vote on the 
proposed M7b release. Post the voting results.

6) If woden-dev vote successful, post to [EMAIL PROTECTED] asking the 
WSPMC to approve a Woden M7b release. Post the voting results.

7) If WSPMC vote successful, post to IPMC at [EMAIL PROTECTED] Be 
specific about timeframe (usually 3 days). Post the results afterwards. 
Success criteria is at least 3 binding IPMC votes (i.e. 3 x +1 from IPMC 
members). Remember, Dims, Sanjiva and Paul F are IPMC members as well as 
WSPMC.

8) If IPMC vote successful, move all the release files from your 
public_html directory to the Woden file space on people.apache.org.

cd /www/people.apache.org/dist/ws/woden
cd milestones
Create a new directory for M7b (e.g. /1.0M7b-incubating)
Move the release files to this new directory 

Copy the file release-notes.html to a new file called README.html in this 
new directory (this will ensure the release notes are displayed after the 
list of files, when this directory is accessed via the web).

e.g.
/www/people.apache.org/dist/ws/woden/milestones/1.0M7b-incubating
...will be accessible via url...
http://people.apache.org/dist/ws/woden/milestones/1.0M7b-incubating/

9) Once again, check that:
* the file permissions are set correctly 
* you can download/unzip the files 
* the downloaded hash digests are correct

10) Update the Woden web site (add the M7b download to the Builds page and 
add a News item announcing the release to the Woden home page).

11) Post a release announcement to woden-dev, [EMAIL PROTECTED] and 
[EMAIL PROTECTED]

12) Final step, which Axis2 folks will do, it to upload Woden M7b binary 
jar to a maven repository...I think Dims can upload to ws.zones.

 Example mailing list posts:
=====================

[VOTE] woden-dev and WSPMC 
http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL 
PROTECTED]

[RESULT]
http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL 
PROTECTED]

[VOTE] IPMC
http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL 
PROTECTED]

[ANNOUNCE]
http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200704.mbox/[EMAIL 
PROTECTED]




regards,
John Kaputin





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to