Funny, I was just drafting a note one this.
Here's what I was planning to do, for the 1.5.4 RC:
1. Announce to the list that I am going to produce a 1.5.4 release
candidate, and get approval from committers to informally "lock" the
subversion tree.
2. Check out the wss4j trunk, and modify the versions in the build.xml
and pom.xml to be "1.4.5-RC1"
3. Build and test the modifications
4. Check in the modifcations
5. tag the tree (again, using 1.5.4-RC1) [1]
6. Revert the versions to "1.5.4-SNAPSHOT", and check in
7. Announce that the tree is "unlocked."
After these steps in subversion, I was going to:
1. Put the release candidate artifacts in my ~/public_html directory,
under stage/wss4j/1.5.4-RC1, or something like that.
2. Create md5 hashes for the release artifacts
3. Digitally sign the release artifacts
[1] I believe that from the point of view of subversion, there's no
difference between a branch and a tag, but tag denotes something
stable, and from which a set of bits can be reproducibly built -- so
I'd vote for tagging, instead of branching.
On Apr 18, 2008, at 11:25 AM, Nandana Mihindukulasooriya wrote:
Hi Fred/Devs,
Sometimes back I created a 1.5.4 branch [1] in the svn, but it
became out dated as we did lot of changes to the trunk. I just
replaced it with the current trunk. Shall we create the release
candidate we planned on this branch. Apache Rampart project is
planning to create a release candidate and this will greatly help as
it can depend on this WSS4J RC.
thanks,
nandana
[1] - https://svn.apache.org/repos/asf/webservices/wss4j/branches/1_5_4/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
