i18n-de

Matt Mackall mpm at selenic.com
Tue Jun 19 17:10:29 CDT 2012


On Tue, 2012-06-19 at 22:23 +0200, Martin Schröder wrote:
> >>>>> Today, I did two things:
> >>>>> - translated most of the fuzzy strings
> >>>> I see you put these on the default branch. I think we've decided to work
> >>>> on released translations on stable instead.
> >>> I'm very sorry, I overlooked that fact. Maybe the wiki isn't clear
> >>> enough about that.
> >> Over the past weeks I considered translating again, but was always
> >> hesitant because I didn't know into which branch to commit. Last time
> >> I committed into the wrong one at the wrong time (some code freeze).
> > There are two ways you can go:
> >
> > a) familiarize yourselves with the content of this page
> >
> > http://mercurial.selenic.com/wiki/TimeBasedReleasePlan
> >
> > and follow the list (or your calendar) closely enough that you know when
> > the freeze is
> >
> > b) always commit on stable
> >
> > The latter has the additional advantage that your changes will always
> > get to users in less than a month.
> >
> > Committing translations to default seems to have almost entirely stopped
> > since February, so I think that (b) is the consensus.
> >
> Matt, so you propose to commit always (even during a code freeze) on
> stable?

Quoting above URL:

        The following changes are accepted on the stable branch (at all
        times): 
        
              * bug fixes 
              * error message improvements 
              * doc fixes 
              * template fixes 
              * improved translations

So yes, always committing i18n changes to the stable branch will never
run afoul of the rules. That's because the code freeze freezes the
_development_ branch.

Again, this is less a proposal at this point than existing practice.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list