tfs2010 - Collaborative merge conflict resolution in TFS 2010 -


i'm responsible doing significant forward-integration on branch i'm not familiar with. i'm comfortable merging majority of conflicts, there areas done me mitigate risk of merge errors. we're running on tfs 2010: options?

our normal workflow communicating changes between developers use shelvesets, tfs disallows shelving of files before merge conflicts resolved...which unfortunate if it's merge conflicts want pass around. know tfs 2010 introduced idea of shared workspace--can feature used multiple people resolve merge conflicts in place?

we have geographically distributed team, unfortunately can't walk on each others' desks. if shared workspaces won't me achieve goal, options?

our team typically pass off section merge developer worked on assuming self-contained (ie merges here not break code inside sln). then, once complete, rest of merge take place. sure 2 steps; however, ensures merge done correctly.

in cases not option, typically have person in charge of merge take note of file or files isn't 100% sure , after merging, , making sure of course project builds, ims / emails team list of files , asks people worked on code review changes. granted, process isn't full-proof @ least how have been handling it.

another solution, eluded to, have tfs shared workspace lives on server of team can remote , review code. here good article describing how set up. if using same shared workspace/mappings etcetera, easier joint merge.

and finally, 1 last option comes mind opt keep local version (do not merge file) assuming not break build , pass off developer. developer, using tf merge /force can force merge pickup fact opted keep local version @ time additional developer resolve merge conflicts.

shelving , unshelving there code reviews why there isn't support conflict resolution. or ms states:

unlike operation, merges reconcilable differences between 2 versions of file automatically , helps merge conflicts manually, unshelve operation not support merges. removing shelved pending changes workspace @ commencement of code review, can assured changes reviewer makes shelveset, such adding comments file, not create merge conflicts during unshelve process.

i understand why doing agree nice have shelve "type" of type merge or affect. surely out when working large projects complicated merges.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -