Okay, I've just given some thought to how we use cvs to tag and branch our releases. Here is what I think we should talk about adopting as our policy.
We should do the following...Lay down rtags (tags on the server) when we do a release (or milestone/beta/rc). This will allow us to get back to that version of source. Then, only when we plan to re-release an old version, should we create a branch from that tag. (We can also create branches for other concurrent dev., but the less branches, the less chance for mistakes) The reason to keep branches to a min is that changes from one branch to not affect another. So if we fix something in 0.8.3 branch, we also need to fix all subsequent branches. Branches also require special changes to the way we as developers work. Summary: TAGS=GOOD; branches =<good. Background: http://www.mail-archive.com/[EMAIL PROTECTED]/msg01732.html http://www.psc.edu/~semke/cvs_branches.html http://owen.sj.ca.us/rkowen/howto/cvs.html#tag ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
