Assuming you tagged 0.2 you can just switch the trunk to that revision If the other changes were minor you could just roll them back.
The terminology and process will differ depending on the solution. Regards Dale Fraser -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Barry Beattie Sent: Wednesday, 23 May 2012 1:46 PM To: cfaussie Subject: [cfaussie] OT: source control question nothing to do with CF, everything to do with correct source code control procedures. say a bunch of work has progressively got to the stage where the last of it to pass testing was v0.2. After that, a bit more functionality was added - twice - to make the versioning v0.2.01 and v0.2.02 and checked in. However, before it could go for testing it was regarded that these two late enhancements were a bad idea and the additional concepts/design were instead incorporated into a new companion product v0.1 (and now v0.1.02). v0.2.01 and v0.2.02 have effectively become red-herrings - they will not contribute to the v0.2 product into the future - it will be the release candidate (and be the 1.0 version of the product) without v0.2.01 and v0.2.02 What to do with them - prune the tree and blow them away? I can't see them being any practical worth. Thoughts? thanks Barry -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
