Restricting users from creating branches...

[phardy at marketguide.comphardy]

> >
> > 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.

That's something we can keep in mind. But for now, if someone wants to 
"experiment", they would already have a copy of the official code in their client 
workspace. Within that workspace, they can do all the experimenting they 
want; but all code checked in must be already tested and approved.

Thanks for the suggestion.


- ----------------
Pat Hardy - Web Developer
Market Guide, Inc (NASDAQ: MARG)
2001 Marcus Avenue S200
Lake Success, Long Island, NY 11042-1011
http://www.marketguide.com
Telephone: 516 327 2400 x228
Facsimile: 516 327 2425