I have 4 developers maintain the same project source code, each of them will accept bugs and then fix the code. The changes must pass QA process then I can release, so I have to review all the files that develper commit to repository and decide which files I have to update to my working copy and then do package.
For example the source files when release1 : A : 1.1 B : 1.1 -> 1.2 C : 1.1 -> 1.2 Then release2 is coming up , the files are A: 1.1 B: 1.1 -> 1.2 -> 1.3 -> 1.4 C: 1.1 -> 1.2 -> 1.3 release2 include A1.2/B1.3/C1.2, beacause B1.4 and C1.3 are new update for next release. so I need a way to update my working copy to release2 files. I'm thinking if developer tag only their change with 'release2_patch' to B1.3/C1.2, then I can update my working copy with -r release2_patch. But when I use 'cvs -q update -r release2_patch' the A1.1 disappear from workinig copy, and B1.3/C1.2 will have sticky tags. Is there any way I can update my working to A1.1/B1.3/C1.2 without sticky tags ? Or a good way to so such kind of linear release scenario ? It is a hard to review the files one by one, beacause in the real case there are 5 hundred files. Even I can find out which files are updated but I still have to review all the updated files. Marco Chen -------------------------------------------------------------- -- View this message in context: http://www.nabble.com/How-to-do-linear-release-with-group-developers---tf4322975.html#a12310409 Sent from the Gnu - Cvs - Info mailing list archive at Nabble.com.
