Content Comparison

...

1. Send release to SPEC RG release manager for publication at  http://research.spec.org/tools.html

Post Release

1. Merge the branche's changes (if such) Create a tag for 1.13
2. Create a branch from the release branch to merge the changes back to master
   (1.13)*$ git checkout master $ git merge 1.7
   1. Create a tag <version-number> (e.g., with gitk)
   Switch to master branch.checkout -b 1.13-back-to-master
3. Update version number in the gradle.properties file (note remember to include -SNAPSHOT!)
4. Execute gradle Execute $ ./gradlew clean distribute -x check -x test to update version strings
5. Update version number in the Eclipse settings (@since tag) .settings/org.eclipse.jdt.ui.prefs
6. Commit the changes Trigger Jenkins buildand push
   $ git commit -am "merging release branch back to master"
   $ git push origin 1.13-back-to-master
7. Create a pull request on GitHub to the master branch
8. Wait for the checks of the pull request to be successful
9. // TODO continue
10. Delete local and remote branch 1.9

       git branch -d 1.9
       git push origin --delete 1.9
    

11. Push tag git push origin 1.9
12. Update version numbers on http://kieker-monitoring.net/download/nightly/

...