Re: Release branch (was Re: Release Status)

2006-12-20 Thread Greg Reddin
Just a question: are you keeping good notes as to what you're doing? I'd like for the details of the process to end up on a wiki page if they are not already there. After reading these messages I have no clue what you are doing :-) Greg On Dec 19, 2006, at 7:49 PM, Rahul Akolkar

Re: Release branch (was Re: Release Status)

2006-12-20 Thread Rahul Akolkar
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote: Just a question: are you keeping good notes as to what you're doing? I'd like for the details of the process to end up on a wiki page if they are not already there. After reading these messages I have no clue what you are doing :-) snip/

Re: Release branch (was Re: Release Status)

2006-12-20 Thread Rahul Akolkar
On 12/19/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 12/19/06, Rahul Akolkar [EMAIL PROTECTED] wrote: snip/ OK, if everyone's fine with that, I will create the 1.0 branch (called SHALE_1_0_x unless there are better suggestions) when we get closer to the release (after all 1.0.4-SNAP

Re: Release branch (was Re: Release Status)

2006-12-20 Thread Craig McClanahan
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote: On Dec 20, 2006, at 2:01 PM, Rahul Akolkar wrote: On 12/19/06, Craig McClanahan [EMAIL PROTECTED] wrote: I would have a mild preference for naming the branch SHALE_1_0 but I'm not going to choke if we go with what you proposed either. I'm

Re: Release branch (was Re: Release Status)

2006-12-20 Thread Greg Reddin
On Dec 20, 2006, at 2:51 PM, Craig McClanahan wrote: * Since the trunk is being continuously built by Continuum, trying to do our release cutting there (including removing SNAPSHOT from the version numbers) would cause Continuum to publish a release, with the real version number, before we

Re: Release branch (was Re: Release Status)

2006-12-20 Thread Craig McClanahan
On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote: On Dec 20, 2006, at 2:51 PM, Craig McClanahan wrote: * Since the trunk is being continuously built by Continuum, trying to do our release cutting there (including removing SNAPSHOT from the version numbers) would cause Continuum to

Re: Release branch (was Re: Release Status)

2006-12-20 Thread Greg Reddin
On Dec 20, 2006, at 7:54 PM, Wendy Smoak wrote: On 12/20/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 12/20/06, Greg Reddin [EMAIL PROTECTED] wrote: So the first thing we'd do when we decide to release is - after finishing up business - start a branch for the release. Then we work

Release branch (was Re: Release Status)

2006-12-19 Thread Rahul Akolkar
On 12/17/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/16/06, Rahul Akolkar [EMAIL PROTECTED] wrote: Sounds like reasonable things to do :-) We even have a staging repo defined in the master pom (thanks Wendy) which we should use for this. By default if the version doesn't end in -SNAPSHOT,

Re: Release branch (was Re: Release Status)

2006-12-19 Thread Craig McClanahan
On 12/19/06, Rahul Akolkar [EMAIL PROTECTED] wrote: On 12/17/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/16/06, Rahul Akolkar [EMAIL PROTECTED] wrote: Sounds like reasonable things to do :-) We even have a staging repo defined in the master pom (thanks Wendy) which we should use for