That sounds workable.
A few questions, though (not likely issues for us, as the tree is
mostly stable):
* I assume any changes to branches/1_5_4 must be merged to trunk
* Conversely, and changes to the trunk made before the release must
be merged to the branch
* It's the release manager's responsibility to ensure these merges
occur
For some reason, I did not get email notification of Nandana's change
to the 1_5_4 branch:
/src/apache/wss4j/branches/1_5_4> svn info .
Path: .
URL: https://svn.apache.org/repos/asf/webservices/wss4j/branches/1_5_4
Repository Root: https://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 649626
Node Kind: directory
Schedule: normal
Last Changed Author: nandana
Last Changed Rev: 649559
Last Changed Date: 2008-04-18 11:00:54 -0400 (Fri, 18 Apr 2008)
But as long as there isn't any further activity on the trunk or
branch, that should work.
Thanks, Ruchith, for the heads up.
-Fred
On Apr 18, 2008, at 12:50 PM, Ruchith Fernando wrote:
On Fri, Apr 18, 2008 at 9:14 PM, Fred Dushin <[EMAIL PROTECTED]>
wrote:
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."
IMHO you do not have to check in the 1.5.4-RC1 changes to the trunk.
This is what we do in the Axis2/Rampart cases:
- We set the branch version to 1.5.4-SNAPSHOT
- Create any RCs from the branch, host the artefacts in your ~/
public_html/....
- Vote on the RCs
- If there are any issues on an RC, do the modifications on the branch
and do another RC
- Once the vote passes tag the revision of the branch that the
successful RC was created as the release with the proper version
numbers (1.5.4 in this case) ... In setting the version number in the
build files of the tag, you should be able to do an svn cp of the
branch with your local changes directly into the tag. This way we
won't have to checking any concrete version numbers to the branch.
If you are 100% certain we will not see any issues with the RC then it
is ok to go with a tag. Otherwise I think we can use the branch.
Thanks,
Ruchith
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]
--
http://blog.ruchith.org
http://wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
