Comments on Effective Thoughts: Rollback a Ooops in TFS with TFPT Rollback

@Nadine I would assume so but before attempting th...

2010-12-14T21:52:46.114-05:00

@Nadine I would assume so but before attempting the rollback, I would clear out your workspace of any merges, edits, check-outs, etc.

I assume the merge candidates already processed be...

2010-12-08T02:55:10.218-05:00

I assume the merge candidates already processed before the rollback will be lost after the rollback. Or will I see them again?

@Michael You simply want to issue the rollback ......

2010-10-25T06:35:58.018-04:00

@Michael You simply want to issue the rollback ... :3. It doesn't matter who committed the previous versions. Note however, the changes committed by others in v4 will be removed as well.

what if I have the following changesets: 6 5 was n...

2010-10-19T17:59:55.405-04:00

what if I have the following changesets:
6
5
was not my project (4)
3
2
1

and I realize that I need to roll back to 2.

Do I issue tfpt rollback /changeset:3 or do issue individual commands (one for each of my changeset numbers (6, 5, 3)?

Interesting. Of course TFPT just wraps TF and TF ...

2010-09-16T16:24:51.628-04:00

Interesting. Of course TFPT just wraps TF and TF is just a command line for doing what you can do in the VS GUI. And, underneath the covers, they're doing the same thing we do now:

Check out; get a specific version of the branch that you want to roll back, undoing local changes when prompted. This checks it all in to the version to which you rolled back.

I thought the instructions he had were longer and more confusing than just doing it the original way.

@Ricardo Ok, uncle! Good points. I'd still be ...

2009-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. :)

the first CYA moment happens automatically - the r...

2009-06-22T17:42:02.060-04:00

the 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 Maybe I'm old school but if I were re...

2009-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?

Re: your comment about choosing "the one prio...

2009-06-22T15:09:53.949-04:00

Re: 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?

Hmmm. Wouldn't it be great if someone created...

2009-06-04T11:01:17.639-04:00

Hmmm. Wouldn't it be great if someone created a nice PowerShell script to do this?