-1 from me - I don't like not giving people a target date to clean things up by. No one has given a proposed date to try and tie things up by - just calling 'hike is tomorrow' out of nowhere doesn't seem right to me.
We have a lot of people working on this over a lot of timezones. I think we should do the right thing and give everyone at least a few days and a weekend to finish getting their issues into 4.1. - Mark On Jan 10, 2013, at 2:36 PM, Steve Rowe <[email protected]> wrote: > I'd like to start sooner than next Tuesday. > > I propose to make the branch tomorrow, and only allow Blocker issues to hold > up the release after that. > > A release candidate should then be possible by the middle of next week. > > Steve > > On Jan 10, 2013, at 2:27 PM, Mark Miller <[email protected]> wrote: > >> >> On Jan 10, 2013, at 2:12 PM, Steve Rowe <[email protected]> wrote: >> >>> I'd like to release soon. What else blocks this? >> >> I think we should toss out a short term date (next tuesday?) for anyone to >> get in what they need for 4.1. >> >> Then just consider blockers after branching? >> >> Then release? >> >> Objections, better ideas? >> >> I think we should give a bit of time for people to finish up what's in >> flight or fix any blockers. Then we should heighten testing and allow for >> any new blockers, and then kick it out. If we need to do a 4.2 shortly >> after, so be it. >> >> - Mark >> --------------------------------------------------------------------- >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
