Gitflow branching model

[Carl Sorensen]

In another project that I am working on they use the gitflow branching
model.

It seems to be quite robust in terms of

a: Freezing features for release while at the same time providing a means
of working on new features.

b: Providing formal methods for getting critical bug fixes into both the
released version and the development version.

c: Clarifying whether bug fixes are part of regular development or
critical fixes for production.

The flow is described here:
http://nvie.com/posts/a-successful-git-branching-model/

I wonder if we should adopt something like this for LilyPond development.

Thanks,

Carl