I know it's a kind of off-topic, but i didn't know any other list to discuss this, may be creating an alternative list to discuss this important subject would be useful :
How are you people are dealing with cvs branches and modules in j2ee projects in real world projects? I'm creating a branching and versioning document for our company. I read jboss "CVS ADMINISTRATION POLICY" (http://www.jboss.org/developers/guides/cvs-admin.jsp), very interesting, i think that almost all of that could apply to j2ee projects in general, but i have some point I'd like to clear : - I'll have a number of modules, like accounting, billing, etc. This modules will have distinct branches? or will them follow a main line? Becouse this would create a exponencial growing of branches, as i would have a branch for each major realease (eg: jboss 2.4, 3.0 and 3.2) times the number of modules. What's the better way to accomplish that? other intersting article published at plop is : Streamed Lines: Branching Patterns for Parallel Software Development http://www.enteract.com/~bradapp/acme/branching/ very worth of reading Thanks in advance and sorry for the off-topic -- Emerson Cargnin SICREDI - Tel : 3358-4860 ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
