Build Master: Progress toward 2.065

[David Nadlinger]

On Tuesday, 10 December 2013 at 13:30:22 UTC, Dicebot wrote:
> Can't agree. Release _tags_ are public. Release branches exist 
> primarily to organize development.

I'm not talking about public in the sense of them being an 
artefact we want to provide to end-users, but just in the sense 
that more than one person might need to work on the release 
branch. As I'm sure you are aware, you'd have to tell everybody 
to reset their local branches every time the upstream one is 
updated. Or do you expect only one person to ever commit to the 
release branch?

Of course, ideally commits would go on the release branch first 
and from there be merged into master (or to other, newer version 
branches). But if the question is how to fix the current 
situation where this isn't the case, I'm not sure that rewriting 
public history is the best option.

David