Reminder: default branch is closed
mg at aragost.com
Thu Jan 26 02:14:47 CST 2012
Matt Mackall <mpm at selenic.com> writes:
> On Wed, 2012-01-25 at 14:19 +0100, Martin Geisler wrote:
>> Matt Mackall <mpm at selenic.com> writes:
>> > This cycle's winner of the "didn't hear about the code freeze" award
>> > is:
>> > changeset: 15978:605ed03b0cbe
>> > parent: 15936:878bc4a62a73
>> > user: Fabian Kreutz <fabian.kreutz at qvantel.com>
>> > date: Sat Jan 21 13:49:46 2012 +0200
>> > summary: i18n-de: Rework and fixes continued
>> > If you're reading this message, check out the stable branch now.
>> (Putting Fabian in Cc.)
>> I've considered to ask the translators to only use the default branch.
>> This gives them a steady flow of changes and no disruptions when default
>> is merged into stable.
> That will result in no i18n changes getting added during freezes. If
> anything, translators should work on the stable branch, where there is
> less message churn?
I was thinking that it would be nicer to have a steady stream of changes
instead of a big change every three months when default it merged into
stable. In that way, it feels like default sees less churn than stable
where you suddenly get lots of new strings 14 days before the release.
It's just a hunch based on the little work I've done on the Danish
translation. It's lagging behind severily and so it makes more sense for
me to only work on the default branch.
If translators are happy to juggle two branches, then that's fine with
Professional Mercurial support
More information about the Mercurial-devel