We are finally getting around to making releases from CVS.
We have a product that is split up into a number of seperate modules. Ideally we would like to be able to release the whole project, or just a module.
I intend to follow the simplest solution here - I'm going to tag all the files with a "release tag" and then do an export. If I'm releasing the whole product I'll put the name of the product as part of the tag; if I'm releasing a single module then I'll put the name of the module as part of the tag. And, of course, if a file is part of a product- and a module- level release, it gets two tags. No problem.
However, I'm a little concerned that if a customer gets a product level release followed by a module level release then the ident string for the module code will not have any relation to the ident string for the rest of the product. The customer will see "rel_tapestry_2_3" (product) and "rel_ta_4_1" (module) and not know which came first.
The best solution I can conjure up is that a module release is always predicated on a product release. So instead of "rel_ta_4_1" (s)he would get "rel_tapestry_2_3_ta_4_1". In effect that makes a module release a sort of patch release.
Andy Jones QA Bod Tapestry Software
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
