Comment 2 for bug 689040

It absolutely _never_ occurred to me that the branch name would change as a result of changing permissions. That is completely counterintuitive. So, yes, I guess this is a duplicate of #190116. Is this at least documented somewhere? Or shouldn't it at least show up on the LP page as a warning when it does happen? I spent a good half hour searching for clues and got nowhere.

Please separate the permissions from the naming. By keeping them coupled, I am now faced with a choice of either disrupting the development team so we can freeze the source tree, or not freezing the source so I can keep people productive. Neither choice is a good one.