I find that it's best to keep the version tree as shallow as possible, with regard to branches. It makes it easier to wrap one's brain around all of the different variants of the project.
The best way I've found to do that is to plan on making the most distant future release from the trunk, and spawn feature and maintenance branches from there. In the event that the code forks before it ships, then by all means release from a branch. But the point here is to trend to merging toward the trunk, not outward. --- Forwarded mail from [EMAIL PROTECTED] I've seen both suggested. I do not want to start a religious war here. Anyone have some links to good docs on the subject? I figure I'll ask the experts before I wade through Google. --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
