title: How to organise development lifecycle with TFVC
body: <p>We're working on a system where we're going to be making a lot of changes over the next year or so.  We use Azure DevOps with TFVC.  Our plan is to develop, test internally, release into a staging environment for the client to test internally, and then release into the live environment once the bugs are ironed out, but we want to do this in fairly small iterations, so we're not releasing massive changes at once and we can get early feedback on changes to make sure we're on the right track and don't get flooded with loads of issues to fix after a big update.</p>
  <p>The problem that is worrying me is that once we've released into the testing environment, it is going to take time for the client to test it, and during that time, we'll have been working on other improvements/bug fixes.  If the client simply says that everything is fine, I can use VS to Get Specific Version as of the time we released the staging version and build and release that to live, but if there are any issues that come up and we need to fix those, we'll end up having to get the client to test all of the new stuff that we've been working on, and we may be in the middle of large changes that aren't practical to release to staging.</p>
  <p>I've looked at TFS branches, but they seem to mess up the paths and be a pain to set up and work with, and I feel like they aren't really for this kind of situation.</p>
  <p>How do people generally solve this problem?</p>
  <p>(I appreciate that many people will argue that Git is a better source control system, but I'm specifically asking how to do it with TFVC)</p>