early code freeze for 1.9?
Matt Mackall
mpm at selenic.com
Thu Jun 2 19:31:53 UTC 2011
On Thu, 2011-06-02 at 09:04 +0200, Adrian Buehlmann wrote:
> On 2011-06-02 07:07, Steve Borho wrote:
> > The amount of API churn on the default branch between 1.8 and 1.9 has
> > been truly impressive. Would anyone object to starting the code
> > freeze (merging default into stable) a week early this time around to
> > give the nightly builds more *soak* time to catch latent problems
> > caused by all this churn?
>
> -1
>
> I don't think this will improve anything but limit development by
> cutting down the most interesting time window for developers.
>
> The truckloads of users isn't using nightly builds anyway, no matter
> what we do on the mercurial side. They all wait for an official release.
>
> Let's stick to the plan.
Unless there's data to indicate otherwise (ie a graph showing a
significant uptick in nightly downloads after the freeze), I tend to
agree.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel
mailing list