anchor.diff:  These release notes using bash command line tools.
   They should work on Linux and MacOS; for Windows, use mSysGit.
   
  -== Obtain Consensus
  +
  +== Preparation
  +
  +=== Obtain Consensus
   
   Before releasing the framework, ensure there is consensus on the xref:docs:support:mailing-list.adoc[dev mailing list] that this is the right time for a release.
   The discussion should include confirming the version number to be used, and to confirm content.
  
positive.code: Make sure you have a JIRA ticket open against which to perform all commits.
  In most cases a JIRA ticket will have been created at the beginning of the previous release cycle.
  
  == Set environment variables
  
  We use environment variables to parameterize as many of the steps as possible.
  For example:
  
negative.code: Note that the branch name is intentionally *not* the same as the eventual tag names (eg `isis-{isisnext}`).
  ====
  
  
  === Create a release branch
  
  The release is performed on a branch; if we are successful, this branch will be merged back into master.
  
  The next step therefore is to create a release branch for the version number being released; eg:
  
  
  [source,bash,subs="attributes+"]
  ----
  git checkout -b $ISISBRANCH
  ----
  
  If necessary, switch to the `core-parent` directory:
  
  [source,bash,subs="attributes+"]
  ----
  