Content Comparison

...

2. Initialize release branch

1. Fetch everything from the remote repository: git fetch
2. Checkout stable: git checkout stable
3. Ensure that the stable branch is up to date: git rebase origin/stable
4. Create a branch for the release:

    git checkout -b $VERSION-RC
   

5. Set the final release version number in the gradle.properties file: kiekerVersion = $VERSION
6. Manually modify the following files: CITATION.cff, codemeta.json
7. Update the copyright year tags in the source files by
   1. Adjusting the year in the updateLicenseHeaderYear task

   2. ./gradlew updateLicenseHeaderYear

8. Modify the HISTORY file

9. Execute a build to update version strings etc.:

   ./gradlew clean distribute -x check -x test 

10. Commit the changes
11. Push the branch

     git push -u origin $VERSION
    

...

1. Save the files downloaded from the Jenkins job. An all-in-one zip can be obtained from https://build.se.informatik.uni-kiel.de/jenkins/job/kieker-monitoring/job/kieker/job/<version>/lastSuccessfulBuild/artifact/*zip*/archive.zip
2. Copy HISTORY to root dir as README unzip kieker-1.11-binaries.zip && cp kieker-*/HISTORY README && rm -rf kieker-1.11/
3. Compute MD5 sums for all files
   1. Linux: md5sum * > md5sums.txt
   2. Mac md5 * > md5sums.txt
4. Compare MD5 sums with the files on Jenkins!

...

4.2 GitHub

• Create a release
• Select the right tagto create a new tag and select the branch
  
• Release name is "Kieker <version>"
• Upload binariesfiles:

Image Added

4.3 Web site (API)

1. Publish API (Javadoc) in https://github.com/kieker-monitoring/api

...

• Prepare artifacts
  • Create kieker-<version>.pom, e.g., from local repo, e.g., ~/.m2/repository/net/kieker-monitoring/kieker/1.15/kieker-1.15.pom
  • Sign files with
    • for f in *; do gpg -u 8E97E26A -ab
    <file>
    • $f; done
  • Resulting set of files:

    • kieker-1.13-aspectj.jar kieker-1.13-emf.jar kieker-1.13.jar kieker-1.13-javadoc.jar kieker-1.13.pom kieker-1.13-sources.jar
      kieker-1.13-aspectj.jar.asc kieker-1.13-emf.jar.asc kieker-1.13.jar.asc kieker-1.13-javadoc.jar.asc kieker-1.13.pom.asc kieker-1.13-sources.jar.asc

• 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)
  • Select Staging upload → Artifact(s) with POM
  • Upload the files from above including the .asc files (note that Sonatype does not ask for it here but will complain later in the staging repository)
  • Select Staging repositories and filter by netkieker and you should see the repository with status open (last time, it was closed already)
  • Inspect the files.
  • 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)!

...