Stefan Küng wrote:
> Stefan Fuhrmann wrote:
> > Stefan Küng wrote:
> >> Stefan Fuhrmann wrote:
> >>>> Should we be rolling a TSVN 1.6.0-RC1 before the main release?
> >>>
> >>> +1 on an RC. It's certainly a good practice to make a test run
> >>> before the final release (make sure everything is in place etc.).
> >>> More importantly it would be a "last chance for test & feedback"
> >>> message to our user base.
> >>
> >> There's not much time for an RC - 1.6 is due next weekend.
> >> And IMHO an RC doesn't make much sense: people who don't use nightly
> >> builds also won't use an RC but rather wait for the final release. And
> >> those who use nightly builds already report problems and test those.
> >>
> >> But if you guys think an RC is necessary: what day should we create the
> >> 1.6.x branch and tag the RC from it?
> >
> > To make any sense, the RC should be out by Monday morning.
> > That basically means branching and building tomorrow (Sunday).
> >
> > If you don't have the time to do it, we can certainly live without an RC.
>
> How about this:
> * increment version number to 1.6
> * branch 1.6.x tomorrow
> * set up the nightly builds for the 1.6.x branch
> * run that 1.6.x build, upload to the nightly build server
> * rename the 1.6.x folder on the server to 1.6.0-RC1
> * send mail announcing the RC to users and dev, no mention of this on
> the website
So be it.
> If possible I'd like to avoid uploading the RC to sourceforge - the
> releaseforge tool doesn't work anymore and it takes me a very long time
> to set the info for every single uploaded file.
People that aren't following the mailing lists are even more unlikely
to look at SF or the web page.
-- Stefan^2.
Received on 2009-03-15 02:42:24 CET