anchor.diff:  +
   [source,xml]
   ----
  -<version>1.14.0-SNAPSHOT</version>
  +<version>1.15.0-SNAPSHOT</version>
   ----
   
   * add the repository definition to pick up the most recent snapshot (we use the Cloudbees continuous integration service). We suggest defining the repository in a `&lt;profile&gt;`: +
  
positive.code: 
  [source]
  ----
  sh interim-release.sh 1.13.6 origin
  ----
  
  where
  
  * `1.13.6` is the base release
  * `origin` is the name of the remote to which you have permissions to write to.
  
  
  
negative.code: 
  If you have commit access to this project (or a fork of your own) then you can create interim releases using the `interim-release.sh` script.
  
  The idea is that this will - in a new branch - update the `dom/pom.xml` with a timestamped version (eg `1.14.0.20160222-0756`).
  It then pushes the branch (and a tag) to the specified remote.
  
  A CI server such as Jenkins can monitor the branches matching the wildcard `origin/interim/*` and create a build.
  