On Thu, Feb 14, 2013 at 12:45 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Thu, Feb 14, 2013 at 12:36:13PM -0500, C. Michael Pilato wrote:
> > As such -- and assuming no one else has a feature waiting in the wings
> and
> > can make a compelling case for further delaying the release to
> accommodate
> > it -- I lean towards branching ASAP. And yes, +1 on delivering alphas as
> > soon as the branch is cut!
>
> We could make backports to the branch a little less of a burden by
> streamlining the process somewhat, e.g. by requiring only two votes
> during the alpha release phase (i.e. until we start issuing betas).
> IIRC we've done this kind of thing before.
>
We have done that before, and I think it worked out well. I
would hesitate to release 1.8 alphas from trunk, but support a streamlined
review process until betas or release candidates start to ship.
I would also urge us to move through the alpha process quickly. From past
experience, it can feel like we're making progress when we release alphas
and betas---and we are, to an extent---but most end users won't start
paying attention until release candidates start to ship and the soak period
starts. (And even then, the vast majority won't start caring until we ship
1.8.0.)
-Hyrum
Received on 2013-02-14 19:53:04 CET