The 1.7 freeze has started!

Martin Geisler mg at aragost.com
Thu Oct 21 03:45:34 CDT 2010


Benoit Boissinot <bboissin at gmail.com> writes:

> On Thu, Oct 21, 2010 at 12:12 AM, Matt Mackall <mpm at selenic.com> wrote:
>> I've merged default into stable. No more commits on the default branch
>> until 1.7 is released (Nov 1), normal rules for stable apply: bug fixes
>> and doc fixes only.
>
> It would be awesome to have a hook at intevation to help prevent
> errors from crew members (I know it happened to me a couple of times
> to apply/push a stable patch on the wrong branch during a freeze).

Should we not just continue like normal: push bug fixes and doc fixes to
the stable branch? Then merge the stable branch back into default once a
day or so.

In 10 days the stable branch will be tagged with 1.7 and we'll begin
putting new stuff on the default branch.

The reason I like this scheme is that it is simple: we just continue
like normal. People who tests the stable branch gets all the bugfixes
right away and people who track default get them too when we merge
stable into default.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/mercurial/


More information about the Mercurial-devel mailing list