anchor.diff:  +
   Finally, commit the version number changes:
   +
  -    git commit -s -a -m "release branch for 2.2.1"
  +    git commit -s -a -m "release 2.2.1"
   
   4. Tag the version and push the tag upstream:
   +
       git tag 2.2.1
       git push origin 2.2.1
  +
  +NOTE: The release branch itself is usually not pushed upstream - you only use it locally to prepare the commit that sets the pom version numbers for the release. Also, the branch is not merged back into the master branch (because we want to keep the SNAPSHOT version number on the master branch). Once you pushed the tag, you can delete your local branch.
   
   == Hotfix releases
   
  
positive.code: +
      mvn versions:set
  +
  This will ask for the new version number. Enter `2.2.1` to indicate that this is the release branch for 2.2.1 release.
  +
  After this is done, execute
  +
  
negative.code: +
      jeenbroekstra merged commit 5d13554 into eclipse:master
  +
  The commit number (5d13554) is what you're after.
  
  3. Add this fix to the release branch by executing the following command:
  +
  