[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [orbit-dev] How to handle RC's?
|
I see there is a lack of response to this message but I think it is because the issue is not clear (at least not to me :)
Why have a branch for an RC? Shouldn't we keep putting 1.0.0 RC builds into the v1_0_0 branch until the official release of 1.0.0? The final release will get tagged and the latest version from orbit should include the proper tag in the qualifier to ensure the version gets rev'd
Are you suggesting that the qualifier of the RC's need to somehow mark that the version is an RC and not the real release? If that is the case we should have a convention for the tagging of RC content such that when we release the official version the tag sorts higher than the RC. Perhaps just tag with v<date>-RCx. When the official release is tagged we would remove the RCx and make sure the date is incremented in the tag.
The other option is to only release official releases into Orbit. I'm not sure if that is an option.
Tom
Chris Aniszczyk---01/24/2008 11:02:09 AM---Anyone have opinions on how to handle RC's for Orbit bundles. For example, imagine a scenario where we have some Library X... w
From: |
Chris Aniszczyk/Austin/IBM@IBMUS |
To: |
orbit-dev@xxxxxxxxxxx |
Date: |
01/24/2008 11:02 AM |
Subject: |
[orbit-dev] How to handle RC's? |
Anyone have opinions on how to handle RC's for Orbit bundles. For example, imagine a scenario where we have some Library X... where the version was 1.0.0 RC2.... how would you want to handle this... besides emailing the author and saying when 1.0.0 was coming out?
v1_0_RC2 as a branch with the bundle version as 1.0.0.qualifier?
v1_0_0 as a branch with the bundle version as 1.0.0.qualifier when 1.0 comes out? That should guarantee that the version would get rev'd probably.
Thoughts?
Cheers,
---
Chris Aniszczyk | IBM Lotus | Eclipse Committer |
http://mea-bloga.blogspot.com | +1.860.839.2465
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev