Rojal Pradhan <[EMAIL PROTECTED]> wrote: > [-- text/plain, encoding quoted-printable, charset: us-ascii, 42 lines --]
> What are the pros and cons of implementing individual task branches? Is > it better to use it or stay away from it? > >From what I know: > Pros: > * Allows developers to checkout and commit their own work without > affecting anyone. That's also a con, because it delays integration of their changes to the mainline. The task branches become just a way to evade the "concurrent" in "concurrent version system". > * They can review their own changes over time before they decide > to merge it to the trunk. > * Re-viewers can check out the individual task branch. > Cons: > * Can clutter up the repository with many tags and branches. That's probably manageable if you keep the branches short. As a rule, I would avoid task branches unless there is a strong possibility that the task will be abandoned. It's easier to undo changes on a branch (by not merging them) than on the trunk. -- pa at panix dot com _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
