Reminder: default branch is closed

[Fabian Kreutz]

Saluton!

Since I push only to the i18n clone, I don't even understand why it is a
problem to do during a code freeze. But true, I didn't hear about a
code freeze. So what should I do better next time?

Bye, Fabian

----- Original Message -----
From: "Martin Geisler" <mg at aragost.com>
To: "Matt Mackall" <mpm at selenic.com>, "Fabian Kreutz" <fabian.kreutz at qvantel.com>
Cc: "mercurial-devel" <mercurial-devel at selenic.com>
Sent: Wednesday, January 25, 2012 3:19:45 PM
Subject: Re: Reminder: default branch is closed

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.

The reason is that we often get a "four lane highway" in the changeset
graph when we have two heads on stable and on default which need to be
merged together with three merge changesets. It would also simplify the
instructions a bit.

When a translation is near 100%, then it can make sense to update it
continiously on both branches, but until then I would be fine with the
translators following a simpler workflow.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://www.aragost.com/mercurial/customer-projects/