-
Notifications
You must be signed in to change notification settings - Fork 2
v1.11.1 suite.2
Geri Jennings edited this page Jan 14, 2021
·
6 revisions
-
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 updates (with issue links):
- cyberark/conjur-oss-helm-chart#60 - PR waiting to be merged
-
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 (with issue links):
- cyberark/conjur-oss-helm-chart#120
- cyberark/conjur-cli#305
- cyberark/ansible-conjur-host-identity#45
- cyberark/ansible-conjur-collection#53 - Add the collection to the suite
-
Create a docs issue to add a new OSS suite release.
Docs issue: cyberark/conjur-docs#1295
-
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
- Conjur product owner reviews and approves the PR. All changes are:
- Complete and usable by users
- Documented
- 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 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.