anchor.diff:  Note that the branch name is intentionally *not* the same as the eventual tag names (eg `isis-{isisnext}`).
   ====
   
  -== Pull down code to release
  -
  -Set the HEAD of your local git repo to the commit to be released.
  -This will usually be the tip of the origin's `master` branch.
  -Then, create a release branch for the version number being released; eg:
  -
  -[source,bash,subs="attributes+"]
  -----
  -git checkout master
  -git pull --ff-only
  +
  +=== 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
   ----
   
  -The release is performed on a branch; if we are successful, this branch will be merged back into master.
  -
  -Check that there are no snapshot dependencies:
  -
  -[source,bash,subs="attributes+"]
  -----
  -grep SNAPSHOT $(/bin/find . -name pom.xml | grep -v target  sort)
  -----
  -
  -The only mention of `SNAPSHOT` should be in the `revision` property of the root `core-prent/pom.xml` file.
  -
  -== Releasing the Framework
  -
  -Switch to the appropriate directory:
  +If necessary, switch to the `core-parent` directory:
   
   [source,bash,subs="attributes+"]
   ----
  
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: These release notes using bash command line tools.
  They should work on Linux and MacOS; for Windows, use mSysGit.
  
  
  == 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.
  