Re: Version numbering

[Steinar Bang <sb@dod.no>]

>>>>> Erik Colson <eco@ecocode.net>:

> A 'release branch' which _only_ holds release commits will soon become
> a problem if one of the devs forgets this and pushes a non-release
> commit to the branch :/

It is possible to limit pushes to a branch to some users (or maybe only
one?). 

If people use rebase before pushing instead of merging then all new
commits should come chronologically after the previous head, and then it
is possible to do a reset on the release branch.

But of course, here we are talking about people messing up, and when
they do, they usually do it in spite of all safeguards you put up.

Worst case, you can delete the release branch, and create a new release
branch from some point in time on master.

On git, recovery is possible... in most cases... just keep calm, and
don't panic.