Branches "best practise"

Hi,

Can anyone offer any best practise advice when it comes to development/bug
fixes and branches/trunk?

Say the Trunk is the main "production ready" code - and we don't want it to
be broken, always build etc. We then have branches, so do you branch per
"bug/incident" and also have a branch for "next feature release" or do you
have one "bugs" branch and developers use that branch when they get assigned
a quick bug fix incident or do you let each developer have a branch?

I can see how any/all of these might work (or a combination of them) - but
we want to go forward with a good workable solution and I hoped that there
are people within this group who have more experience than us and are
willing to share some of the pain that they may have gone through by taking
(perhaps) an incorrect path that we may have outlined above?

Any help/comments much appreciated.

Thanks a lot.

Bren

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2778131

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-06-27 16:23:10 CEST