Restricting users from creating branches...

[RichardBrooksbyrb at geodesic.com]

At 09:14 1998-06-24 -0400, phardy at marketguide.com wrote:

> > I'm curious.  Why do you want to stop developers creating branches?  I
> > would have thought it would be more dangerous to your code's integrity to
> > have them merging without authorization.  Can you explain the situation?
>
> We only want certain people authorized to maintain codelines. There will be 
> less of a hassle propagating changes from one codeline to another. It'll
> also cut down on unnecessary disk space used, regardless of whether or
> not disk space is cheap. In addition, the authorized code branchers will
> always know how many branches we have for what releases and why. It's
> more of a maintenance thing.

That's interesting.  I'm _encouraging_ people to make branches if they want
to do experimental or prototype work, so that it doesn't damage the quality
of the "master" codeline.  Authorized changes are done on branches too, and
only merged into the master codeline when they have been reviewed and
tested.  The idea is to maintain the quality of the master codeline so that
it is always of releaseable quality.