Versions Compared

Version Old Version 11 New Version 12
Changes made by

Andre van Hoorn

Andre van Hoorn

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Note that the  kieker-RC-release already pushed the file to the Staging Repository
  • Inspect and publish release in Staging Repository (see also  8a. Release It (Sonatype User Guide) )
    • Login to  https://oss.sonatype.org/index.html#stagingRepositories (with  Sonatype JIRA credentials)
    • Filter by netkieker and you should see the repository with status open
    • Inspect the file and trigger the "Close" operation. An email will be sent, which contains SHA1 checksums to be compared
    • Inspect the snapshot repository (Refresh Staging Repositories view and the repo should appear with Status Closed)
    • If everything's fine, trigger the "Release" operation. Note that this step is irreversible (i.e., a file once published at Maven Central cannot be replaced)!
  1. Jenkins cleanup:
    1. Disable the jobs  kieker-RC and  kieker-RC-release

6. Announce Release

  1. Update web site (Sometimes easiest to search/replace in separate editor):
    1. Side menu (via WordPress "Appearance->Menues")
    2. http://kieker-monitoring.net/download/ (note that web gui may not be available, yet)
    3. http://kieker-monitoring.net/download/nightly/ (note that web gui may not be available, yet)
    4. http://kieker-monitoring.net/release-notes/
    5. Upload user guide to  http://eprints.uni-kiel.de/16537/ and move to top position in list (arrows)
    6. http://kieker-monitoring.net/documentation/
    7.  http://kieker.uni-kiel.de/trac/wiki/releases#TemplateforaScheduleTowardsaRelease
    8.  http://kieker.uni-kiel.de/trac/admin/ticket/milestones (Set completion date; set default to next release; add second-next release as milestone)
    9.  http://kieker.uni-kiel.de/trac/admin/ticket/versions (Add released version, + next-SNAPSHOT and set to default; remove old SNAPSHOT)
    10. Update Kieker calendar (if new release dates added)
    11. http://kieker-monitoring.net/documentation/quickstart-guide/ (+ Eclipse version)
  2. Create news post on  Kieker web site. Template:
    Title: Kieker <VERSION> released
Body:  
On October 1, 2015, we released version 1.12 of our Kieker framework for application performance monitoring and dynamic software analysis. As usual, the release is available for download at http://kieker-monitoring.net/download/.

PASTE HISTORY FILE

For details and download see http://kieker-monitoring.net/
  3. Send mail to users and develops list (template above)

...

Post Release

  1. Create a tag for 1.13 (for instance, with gitg)
  2. Create a branch from the release branch to merge the changes back to master
    (1.13)*$ git checkout -b 1.13-back-to-master
  3. Update version number in the gradle.properties file (remember to include -SNAPSHOT!)
  4. 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 and 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/

...