anchor.diff:  
   include::temp-properties-files-for-site/attributes.adoc[]
   
  -== Apache Tamaya: Release Guide
  +:sectnums: yes
  +
  += Apache Tamaya: Release Guide
   
   Performing a release requires several steps. This document describes each step, so everybody in the committer's
   team should be able to perform the release procedure.
   
   
  -=== Tell the others you would proceed with the release procedure
  -
  -[listing,text]
  -----------------------------------------
  -    first steps for the next release
  -
  -    hi @ all,
  -
  -    if there are no objections, i'll start with the first steps for the next release (review, documentation,...).
  -    it would be great to start with the release procedure next week.
  -
  -    regards,
  -    [name]
  -----------------------------------------
  -
  -
  -=== Check everything is ready
  +== Tell the others you would proceed with the release procedure
  +
  +[listing,text]
  +----
  +first steps for the next release
  +
  +Hi @ all,
  +
  +If there are no objections, I'll start with the first steps for
  +the next release (review, documentation,...).
  +It would be great to start with the release procedure next week.
  +
  +Best regards,
  +[name]
  +----
  +
  +== Check everything is ready
   
   * Check the jenkins builds.
   * Ensure all JIRA-tickets targeting the release are resolved. If not, get in contact with the ticket
  
positive.code: * Rename the vote branch:
  
  [listing,text]
  ----------------------------------------
      git branch -m vote01-tamaya-[release-version] tamaya-[release-version]
  ----------------------------------------
  
  * Add a release tag:
  
  ----------------------------------------
      git tag -a tamaya-[release-version]
  ----------------------------------------
  
  * Merge master with the new prepared version:
  
  [listing,text]
  ----------------------------------------
      git checkout master
      git merge tamaya-[release-version]
      git push origin tamaya-[release-version]
      git push origin master
  ----------------------------------------
  
  * Close the release and corresponding tickets at JIRA
  
  * Wait some minutes and check `http://repo2.maven.org/maven2/org/apache/tamaya`
  
  * Upload the distribution Artifacts
  
  [listing,text]
  ----------------------------------------
      svn co https://dist.apache.org/repos/dist/release/incubator/tamaya/
      mkdir [version]
      // add and commit the artifacts (*source-release.zip, *bin-release.zip + asc, md5, sha1)
      // use the artifacts from:
      //  http://repo1.maven.org/maven2/org/apache/tamaya/tamaya-distribution/[version]/
  ----------------------------------------
  
  
  === Updating the Tamaya Project Site
  
  Basically the new site should be directly deployable, just execute
  
  [listing,text]
  ----------------------------------------
  mvn site site:deploy
  ----------------------------------------
  
  
  === Announce the new version
  
  Announce the new version on @TamayaConf and other social media channels. Also drop a short mail on the amiling list.
  
negative.code:   ** how long it takes to resolve it and if one can help.
  
  
  == Prepare the release
  
  * Create release notes and commit them to `tamaya/readme/` (format `ReleaseNotes-[version].html`)
  * Create a release branch in git and switch to this branch:
  
  
  === Using the Release Plugin
  
  For performing the release you can use the maven release plugin:
  
  [listing,text]
  ----
  $ git checkout -b vote-tamaya-[release version]
  $ export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=200m"
  $ mvn release:prepare -DdryRun=true -DperformRelease=true
  # optionally pass GPG params for signing with: -Darguments="-Dgpg.keyname=1336D3E6 -Dgpg.passphrase=XXXXXX"
  # copy prepared workspace (to continue faster if an upload fails in the next step)
  ----
  
  * If something fails you may switch to the master branch, fix whatever is needed and rebase your release branch to
    accommodate the latest changes done.
  * On success you can check the release packages from `dist/target`.
  * If everything looks good you can proceed with the release:
  
  [listing,text]
  ----
  $ export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=200m"
  $ mvn release:prepare -DperformRelease=true
  $ mvn release:perform -DperformRelease=true
  ----
  
  === Preparing the release without the Release Plugin
  
  The release plugin is great, but in some cases it breaks even, when release:prepare -DdryRun=true was successful.
  Preparing the release vote without the release plugin is stright forward:
  