title: TFS Shelvesets and Code review
body: <p>One of the reasons for using TFS shelvesets is for code review which I don't agree, but this is the practice followed in my current project. The reason I see using TFS shelvesets is not a good idea for code review are</p>
  
  <ul>
  <li>Shelvesets do not have a natural ordering as change-sets have. This
  can lead to lots of merge conflicts. </li>
  <li>If developer cannot checkin code until it gets reviewed, it puts a dependency on the reviewer, and if the reviewer does not do review within a short duration these shelvesets
  can interfere with other tasks.</li>
  <li>Collaboration with other devs becomes pain as now you need to pass shelvesets around rather than checkin code which can again cause merge conflicts in future.</li>
  </ul>
  
  <p>Can someone provide me some pointers which can be either <strong>for</strong> or <strong>against</strong> the TFS shelveset approach for reviews so either I get convinced about the approach or I can present a case for not using this approach?</p>