Enable "hg push --new-branch" by default in hgrc

[Dominik Psenner]

> -----Original Message-----
> From: Mads Kiilerich [mailto:mads at kiilerich.com]
> Sent: Friday, March 25, 2011 11:02 AM
> To: Dominik Psenner
> Cc: 'Mercurial Developers'
> Subject: Re: Enable "hg push --new-branch" by default in hgrc
> 
> On 03/25/2011 08:56 AM, Dominik Psenner wrote:
> > I've got another usecase for "issue" named branches. A bugtracking tool
> > could easily gather changesets related to the issue identified by
> IssueId
> > and link to those changes by invoking something like:
> >
> > $ hg log -b IssueId
> >
> > Would you please tell me more about possible scalability problems and
> > (computational) borders that can be encountered?
> 
> Mercurial will frequently iterate through branches, heads, tags and
> bookmarks. Contrary to that, revisions are usually not iterated. Lots of
> revisions is thus not a problem, but a similar number of branches might
> be.

That makes sense and anticipating the branching frequency is hard.
Calculating the median gives about 15 issues a month, equalling 180 issues a
year. Thus we would breach the thousands mark in about 5.5 years. Do you
think that could become a problem some day, without taking Moore's law into
account? :-)

We use to close named branches when they're resolved. Does mercurial treat
closed branches equally to active/inactive ones?