title: GitFlow: How to maintain previous releases?
body: <p>I am currently working on a workflow for my team.
  A suggestion we received was to use the GitFlow scheme. This scheme can be put on a chart as follow:</p>
  <p><a href="https://i.stack.imgur.com/vEAlo.png" rel="noreferrer"><img src="https://i.stack.imgur.com/vEAlo.png" alt="gitflow" /></a></p>
  <p>However, I have one question about how to manage a specific case.
  Because of our activities, we have to maintain previous versions that our customer may still be using and does not want to update for various reasons.</p>
  <p>In the GitFlow scheme, the trunk is supposed to be where the releases happens. A commit in the trunk is a potentially ship-able product and should receive a version tag.</p>
  <p>So ... how can I go back in time, produce a fix for an older version and merge it back in the trunk in order to produce that release ?</p>
  <p><a href="https://i.stack.imgur.com/3BXqs.png" rel="noreferrer"><img src="https://i.stack.imgur.com/3BXqs.png" alt="GitFlow hotfix on released branch" /></a></p>
  <p>An another question if I do not want that fix to be brought back in the trunk ?</p>
  <p>It seems to me that this workflow is more adapted to software that continually pushes new versions to their customers, such as mobile apps, but not industrial products, even if they are built from a CI. But maybe I am missing something here, hence my question</p>