Definitely, finish up the current release before we start betas for 1.5 I figured 1.5 has a few glaring things we need to patch up before we start shipping betas for it anyway - I just want people to be thinking about it as something that can be released :)
-- Steve On Jul 26, 2011, at 3:38 PM, Eric Richie wrote: > I'd like to STRONGLY disagree on this one. We already have nighties for 1.5, > I'd really prefer to hold off on a beta for 1.5 until we have 1.4.3 out the > door. (It's sooo close!) > > The last time we tried multiple versions in beta at the same time, it turned > into a mess and everyone jumped right to the new hotness. Then they both > languished for way too long. > > I know that new is awesome but the sooner we can get 1.4.x wrapped up, the > sooner we can move forward without looking back! > > (And of course not being 'beta' yet doesn't stop anyone from working on other > things in another branch.) > > -Eric > > On Jul 26, 2011, at 6:28 PM, Stephen Holt wrote: > >> Hey all, >> >> 1.4.x seems to be going pretty well, and we've got some exciting new shiny >> things to play with in Lion now. But, to keep momentum going, I propose we >> start driving the defect count on 1.5 branch for betas and eventual release. >> >> This implies any feature branches will remain unmerged until 1.5 is out. >> >> My main desire with this is to keep momentum going in the project. >> >> Just my 2ยข. >> >> >> -- >> Steve > >
