4.5.0 - Release checklist

Keama Release Checklist

1. Gitlabab pipeline results:

   1. Check Gitlab build job for failures
   2. Check Gitlab pytest job for failures

2. Tarball preparation:

   1. If this is the release of the final version, please check the sanity check ticket of the previous release and make sure all comments are addressed
   2. bump up version in configure.ac
   3. bump up version in tests/test_keama.py:test_version() (#40)
   4. Note release in changelog
   5. check the date in LICENSE
   6. Check README file (including installation details)
   7. update copyrights in all touched files using a simple script in qa-dhcp.
   8. Do autoreconf -i on a modern system, test the code compiles and push your changes.

3. Build tarball, packages and docker image

   1. Go to keama-tarball > Build with Parameters, in field keamaBranch put in release branch and run the job, this will build release tarball and save it as an artifact of the job
   2. Go to keama-pkg > Build with Parameters, in field keamaBranch put in release branch and run the job, this will build release packages and save it as an artifact of the job (baseBranch should be 'master' if not using custom qa-dhcp branch)
   3. Go to keama-docker > Build with Parameters, in field keamaBranch put in release branch and run the job, this will build release tarball and save it as an artifact of the job (keamadockerBranch should be 'master' if not using custom keama-docker branch)
   4. Go to keama-release-notes > Build with Parameters, in field version put in release version and run the job, this will build release notes in txt format and save it as an artifact of the job.
   5. before tarball will be deemed as ready to release it will be release candidate. Each consecutive respin will have it's own name starting from -rc1
   6. open a ticket in keama repo called release X.Y.Z-rcX sanity checks and put there location of release tarball, packages, and docker image
   7. wait for team input about new tarball, if respin is needed go back to Build tarball point also increasing release candidate number
   8. if tarball is accepted create a tag of this version on a last commit in release branch and kea-docker repo
   9. move tarball and release notes to non release candidate location (e.g. moving to /data/shared/sweng/keama/releases/4.5.0)
   10. make sure that new release directory allow group write e.g. chmod 665 /data/shared/sweng/dhcp/releases/4.3.2b1
   11. upload packages to cloudsmith
   12. upload docker image to cloudsmith
   13. open tickets to address issues mentioned in sanity checks IF those were not already fixed and close sanity check ticket

4. Signing and notification

   1. Sign the tarball and put signature files with the tarball
   2. notify support about readiness of release, at this point QA and dev team work is done

5. Post release

   1. mark jenkins jobs to save forever.
   2. Bump version in configure.ac, tests/test_keama.py:test_version() (#40)and do autoreconf -i
   3. push to repo and unfreeze the code

6. Releasing tarball

   • (Support) Wait for clearance from Security Officer to proceed with the public release (if applicable).
   • (Support) Confirm that the tarballs are signed correctly.
   • (Support) Place tarballs in public location on FTP site.
   • (Support) Publish links to downloads on ISC website.
   • (Support) Write release email to dhcp-announce.
   • (Support) Write email to dhcp-users (if a major release).
   • (Support) Update tickets in case of waiting for support customers.
   • (Marketing) Announce on social media.
   • (Marketing) Write blog article (if a major release).