RE: Re: Find out which branches exist

> Er, only if people check broken code into the trunk. I agree
> that big, experimental changes might require branching, but
> Subversion, for example, seems to work fine with everyone
> checking into the trunk. A decent test suite and continuous
> integration should let you reliably check into the trunk.
>
Actually, we have a branch for every defect or new feature. We usually
have teams working on either of these and a branch is the only way they
can share their changes without breaking the trunk or otherwise
de-stabilizing it. If you have a small team, you can probably get away
with working directly on the trunk, but larger teams usually need to use
branches.

To answer the original question, we have a closed-branches directory
where branches are moved when development work is done on them. So at
any given time, you can see which branches are open by looking in the
branches directory.

> Cheers,
> Mike.

Cheers,
Craig

--
Craig L. Ching
Chief Product Architect
IBM Certified Specialist, MQSeries
IBM Certified Developer, MQSeries
MQSoftware, Inc.
(952) 345-8720
www.mqsoftware.com 
 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org