Flagging stable patches

Martin Geisler mg at lazybytes.net
Mon Jul 13 10:40:06 CDT 2009


Dirkjan Ochtman <dirkjan at ochtman.nl> writes:

> On Mon, Jul 13, 2009 at 15:29, Martin Geisler<mg at lazybytes.net> wrote:
>> I think there has been some confusion (at least from my side) about
>> just what should go into crew-stable and what should go into crew.
>>
>> It used to be so that only *important bugfixes* went into crew-stable
>> and everything else went into crew. It was rare that stuff got into
>> crew-stable and I didn't even have a crew-stable clone on my machine
>> for a long time.
>>
>> But after 1.3, Matt has indicated that the defaults have changed. As
>> I understand it, we now push *straight-forward bugfixes* to
>> crew-stable and everything else to crew. In that way, crew-stable is
>> in perpetual feature freeze.
>
> AFAIK, that has always been the case.

Yeah, I agree about the feature freeze. But I don't think I pushed
pushed documentation fixes to crew-stable before :-)

>> I guess that also means that I can base mercurial-i18n on stable
>> since that repository will see more updates now? But then the "big
>> re-wrapping" patch should have gone into crew, otherwise translators
>> will only see it shortly before the next major release :-/
>
> I think you're going to need two i18n repositories, unless you want
> translators to translate all the new strings during the feature
> freeze.

That was my plan -- if we have a longer feature freeze in hg-stable,
then I think it will work out nicely. It would give the translators a
stable target within each point release, and a somewhat larger change
after the push at the beginning of the feature freeze.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090713/6c26a0d7/attachment.pgp 


More information about the Mercurial-devel mailing list