| Mercurial branches
| are a bit more permanent than git-branches. What makes sense to me is
| that example, two separate branches, and to use tags to mark releases,
| not a whole separate branch per stable release, especially seeing how
| we don't backport bug fixes to several stable releases, only to the
| last one.
I probably just don't get version control, but to me that doesn't seem
to model what is actually going on, which is that when we make a
release, there is actually a fork in the development. At the end of a
release series, that branch is essentially abandoned. It doesn't make
sense to me to continue with it once the release series is obsolete.