Reminder: default branch is closed

Matt Mackall mpm at selenic.com
Wed Jan 25 12:22:38 CST 2012


On Wed, 2012-01-25 at 21:08 +0300, Alexander Sauta wrote:
> > 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.
> ...
> > 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.
> 
> Russian translation is about 100% ready, so I've pushed to default
> branch. Do I need to merge stable branch into default during the code
> freeze as it's written in wiki guidelines, just leave it?

Merging into default would create a commit on default, which is not
allowed because the default branch is closed.

Why is it 'closed'? Because it reflects the rules of the freeze: only
changes that are suitable for stable are allowed right now, so there's
no purpose to putting a change on default.

And this gets us back to the purpose of the freeze: to focus everyone's
attention on preparing a good release: testing, bug fixes, getting rid
of sharp edges. If you are committing on default, it means you're not
doing that.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list