tag:blogger.com,1999:blog-9369362.post1370490530262092667..comments2009-06-23T07:11:01.191-04:00Jeff Hunsakerhttp://www.blogger.com/profile/07740484450068986098noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-9369362.post-3758936154108754042009-06-23T07:11:01.191-04:002009-06-23T07:11:01.191-04:00@Ricardo Ok, uncle! Good points. I'd still be careful about wacking modifications made between the original and the rollback. Developers are sneaky. :)Jeff Hunsakerhttp://www.blogger.com/profile/07740484450068986098noreply@blogger.comtag:blogger.com,1999:blog-9369362.post-44759602421021312362009-06-22T17:42:02.060-04:002009-06-22T17:42:02.060-04:00the first CYA moment happens automatically - the rollback itself is a check-in/changeset; it's now part of version history. CYA #2: add a comment to the rollback check-in. CYA #3: associate the check-in with the work item you created the moment they asked you to remove the feature. Regarding functionality added since that rollback moment... that's the part where you have to cross your fingers. :) But my experience w/ this feature-rollback scenario so far has been [suprisingly] successful.Ricardo Wilkinshttp://www.blogger.com/profile/00012656566305502851noreply@blogger.comtag:blogger.com,1999:blog-9369362.post-38282743257384012632009-06-22T15:17:04.419-04:002009-06-22T15:17:04.419-04:00@Ricardo Maybe I'm old school but if I were removing functionality, I would want to create a new work item and merge that removal into the history. Probably more CYA than anything but it's a data point which would be shoved under the rug if we did a rollback. I'd want to be able to log/audit this feature removal b/c "Well, Ms. Sponsor, we're 2 weeks late b/c we were asked to add and remove this feature 4 times. See here on this report...? It shows Mr. Product Owner approving this work item and re-opening it 4 times." Also, what about functionality added in those past three weeks?Jeff Hunsakerhttp://www.blogger.com/profile/07740484450068986098noreply@blogger.comtag:blogger.com,1999:blog-9369362.post-90321166207946563652009-06-22T15:09:53.949-04:002009-06-22T15:09:53.949-04:00Re: your comment about choosing "the one prior to the version you want to rollback to..." - would you agree that rollback is not just important for moving the codebase back to a previous state, but is also important when an 'undo' of a feature or change to the code is necessary? Thus, that could mean a rollback of a small changeset that was checked in 3 weeks ago, for example. Of course, testing now becomes more important. Would you agree, or is this bad practice?Ricardo Wilkinshttp://www.blogger.com/profile/00012656566305502851noreply@blogger.comtag:blogger.com,1999:blog-9369362.post-8574054169605789562009-06-04T11:01:17.639-04:002009-06-04T11:01:17.639-04:00Hmmm. Wouldn't it be great if someone created a nice PowerShell script to do this?Rob Strenonoreply@blogger.com