Skip to content

v1.10.0 suite.1

Jump to bottom
Geri Jennings edited this page Oct 28, 2020 · 8 revisions

Release v1.10.0+suite.1

Release checklist

  • Check the Jenkins dashboard to ensure builds are green.

  • If any builds have recently not been green, review the project and determine whether updates are required pre-release.

    Components requiring updates pre-suite release:

  • Review the unreleased changes in the wiki. Determine whether any additional releases will be required before creating a new suite release.

    Components requiring releases pre-suite release:

  • Create a docs issue to add a new OSS suite release.

    Docs issue: [cyberark/conjur-docs#1208](https://github.com/cyberark/conjur-docs/issues/1208

  • Create a PR to update the suite.yml to include updated versions. Include a draft of the markdown release notes by running the following command in your release branch:

    summon -p keyring.py \
  --yaml 'GITHUB_TOKEN: !var github/api_token' \
  ./parse-changelogs \
  -v {suite release version} \
  -t release \
  -o RELEASE_NOTES.md

    PR link: [cyberark/conjur-oss-suite-release#188](https://github.com/cyberark/conjur-oss-suite-release/issues/188

  • Conjur product manager reviews the PR and adds "What's new" text in a comment.

  • PR is updated to include "What's new" text.

  • Conjur maintainer reviews and approves the PR, ensuring the PR checklist is complete for a release.

  • Conjur product owner reviews and approves the PR.

  • Conjur maintainer merges the PR and creates a tag.

  • Conjur maintainer copies the HTML release notes from the draft release to the docs issue.

  • Technical writers publish the release notes.

  • Conjur maintainer publishes the draft GitHub release.

Clone this wiki locally