title: How to manage release branches
body: <p>We are trying to manage multiple release branches using git. Our branch organization is typical. Primary on-going development is on master. Topic branches are used for work and merged into master. Master is the next major release. However we also work on interim releases (dot releases). For example, master will be working towards version 7.4 while we are also working on 7.3.2. </p>
  
  <p>Naturally, most (all?) of the work done for 7.3.2 must be in 7.4. That is most, of the work done for the 7.3.2 release branch must also be done for the master (ie 7.4) release branch.</p>
  
  <p>What are some techniques that you use to manage these branches? In particular, ensuring that changes are merged into both branches? </p>
  
  <p>Our solution has been to create parallel topic branches. Once a topic has been completed on one or the other of the release branches, it is copied to another topic branch from the other release branch, using <code>cherry-pick</code> or <code>rebase --onto</code> or sometimes even a manual diff and merge. </p>
  
  <p>This process covers the mechanics. How do others ensure that the mechanics actually occur? How do you verify that a change has been made to both (many) release branches?</p>
  
  <p>Thanks for your suggestions</p>