[PATCH 0 of 2] keyword: bugfix when all changes in a file were recorded (2nd try with test)

Christian Ebert blacktrash at gmx.net
Tue Jun 1 10:21:25 CDT 2010


* Matt Mackall on Tuesday, June 01, 2010 at 09:30:01 -0500
> On Tue, 2010-06-01 at 15:07 +0200, Christian Ebert wrote:
>> * Christian Ebert on Tuesday, June 01, 2010 at 03:45:19 +0200
>>> I hope it's not too late for this fix to go into 1.5.
>> 
>> Oh, should be 1.5.4, but that's only stable, right? Then sorry
>> for having been a nuisance, can be fixed in crew for 1.6 ... I'm
>> still slightly confused about the release policy.
> 
> I've queued these in the default branch, as they don't apply to stable.

It dawned on me, once the ohmegod-a-bug-panic subsided, again
sorry for having pestered you. 

> The _schedule_ is: releases every 1st of the month. Major releases off
> the default branch in March, July, and November (every four months) and
> minor releases off the stable branch in all the other months. We'll also
> cut minor releases for serious bugs (see 1.5.3).
> 
> The _policy_ is: bug fixes, doc improvements, and i18n updates are
> always acceptable for stable, everything else goes in default. During
> the release code freeze, default works like stable.
> 
> You'll notice we let the new hgeol extension into stable. This is also
> allowed as a) it's gotten sufficient testing and b) there's no way it
> can regress people's existing workflow as it's disabled by default and
> has no code impact outside itself.

Thanks for taking the time to explain.

c
-- 
theatre - books - texts - movies
Black Trash Productions at home: http://www.blacktrash.org/
Black Trash Productions on Facebook:
http://www.facebook.com/blacktrashproductions


More information about the Mercurial-devel mailing list