anchor.diff:  +
       git push origin releases/2.1.6
   
  -Bug fixes are typically added to a hotfix release branch by https://git-scm.com/docs/git-cherry-pick[cherry-picking] the relevant commits from the _master_ branch. 
  +Bug fixes are typically added to a hotfix release branch by https://git-scm.com/docs/git-cherry-pick[cherry-picking] the relevant commits from the _master_ branch.
   
   This works as follows:
   
  
positive.code: 
  1. The project's https://www.eclipse.org/projects/handbook/#ip-iplog-generator[IP log] needs to be filed and approved by the Eclipse legal team;
  +
  The IP log can be automatically generated and submitted to the legal team. Obtaining approval may require several days, so it's good practice to submit this at least two weeks before the planned release date. 
  2. The project's https://projects.eclipse.org/projects/technology.rdf4j[review documentation], part of the application, needs to be in order. 
  
  Typical review documentation can be a simple reiteration of the most important new features, a link to the issue tracker/release notes and documentation, and a remark about compatibility (if applicable). Once the review documentation is up, a mail needs to be sent to technology-pmc@eclipse.org to ask for approval. Here's an example of such a message, which was to get approval for the RDF4J 2.2 release:
  
  ----
  Dear PMC members,
  
  Can I get your approval for RDF4J release 2.2, scheduled for February 2. 
  
  Release review info: https://projects.eclipse.org/projects/technology.rdf4j/reviews/2.2-release-review 
  
  Issue tracking the release: https://bugs.eclipse.org/bugs/show_bug.cgi?id=510577
  
  
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:
  +
  