title: Closing the project in Azure DevOps
body: <p>We have multiple small projects within our organization. Ever since we adopted Azure DevOps recently, we started creating the individual Azure DevOps projects for everyone of these projects. The ALM process has been going on very well, with end to end traceability established with in the online tool.</p>
  <p>However, as we get to end of each of these projects, we started to realize that these individual project and its code needs to be maintained further for the bug fixes and hotfixes. Unfortunately, Microsoft doesn't give a clear road-map for a project code, once it is completed.</p>
  <p>Since we have a separate devops project for all the maintenance applications, this becomes much more confusing.</p>
  <p>So, Could you suggest me on what is the best practice to maintain the code after the project is completed? Here are some options that I can think of.</p>
  <ol>
  <li><p>Just keep the code in the same project and keep doing the bug fixes there. But, this will create an administrative nightmare to keep track of multiple projects for our maintenance application landscape (especially, since we already have a single projects with multiple repos and teams maintained).</p>
  </li>
  <li><p>Migrate the code from the completed project repository to the maintenance project. But, this again is a migration from one repo to another. So, I am not sure if this is right.</p>
  </li>
  </ol>