message changes on crew-stable

Martin Geisler mg at lazybytes.net
Thu Sep 17 16:47:02 CDT 2009


Wagner Bruna <wagner.bruna+mercurial at gmail.com> writes:

> On Thu, Sep 17, 2009 at 12:52 PM, Greg Ward <greg-hg at gerg.ca> wrote:
>
>> If no one objects to that, I'll send a patch relative to crew-stable.
>
> Well, I've got one objection :-)  That message change will invalidate
> all translations for a relatively important help text. It's probably
> not a big deal for most -stable translations at the moment, but pt_BR
> is practically completed.
>
> I could update that translation right now, but all message changes on
> crew-stable must reach hg-stable before their translations can be
> updated. And usually Matt pull changes from crew-stable and
> i18n-stable just before a point release, so the time window for
> translation updates to late changes on crew-stable is usually quite
> small (sometimes even nonexistent).
>
> I'd suggest either applying -stable message changes directly to
> i18n-stable, or updating -stable translations directly on crew-stable.
> Martin, what do you think?

Good question... with the current system hg-i18n and hg-i18n-stable
synchronize with hg and hg-stable (respectively), so Matt can always
pull from them before a release.

However, looking at the releases back to version 1.0, it looks like
crew-stable is pulled into hg-stable just before a release anyway. Then
it would make good sense to let hg-i18n-stable track crew-stable.

-- 
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/20090917/ed481975/attachment.pgp 


More information about the Mercurial-devel mailing list