mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-22 09:57:41 +00:00
Code Issues Releases Wiki Activity

Edit release_checklist.md to add an item to update the security versions on...

Browse Source
This commit is contained in:
Vicky Risk 2025-07-31 08:44:36 -04:00 committed by Andrei Pavel
parent 15d5daa9b1
commit 8da73b894a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.gitlab/issue_templates/release_checklist.md
View File

@ -194,9 +194,9 @@ Now it's time to publish the code.
1. [ ] Write blog article (if a major release). 1. [ ] Write blog article (if a major release).
1. [ ] Check that the tarballs are available on Cloudsmith, since we are downloading from there, not downloads or ftp. 1. [ ] Check that the tarballs are available on Cloudsmith, since we are downloading from there, not downloads or ftp.
1. [ ] Publish links to downloads on the ISC website. Update release dates. Check the modal messages and update if necessary. 1. [ ] Publish links to downloads on the ISC website. Update release dates. Check the modal messages and update if necessary.
1. [ ] <mark>Security Release Only</mark>: Update the security releases version table in the downloads data file on the website. This information is used by Stork to flag new security versions.
1. [ ] <mark>Stable Releases Only</mark>: If it is a new `major.minor` version, SWENG will have created a new repo in Cloudsmith, which will need the customer tokens migrated from an existing repo. Verify that the KB on installing from Cloudsmith has also been updated. 1. [ ] <mark>Stable Releases Only</mark>: If it is a new `major.minor` version, SWENG will have created a new repo in Cloudsmith, which will need the customer tokens migrated from an existing repo. Verify that the KB on installing from Cloudsmith has also been updated.
1. [ ] If a new Cloudsmith repository is used, make sure that the Zapier scripts are updated. * If the tokens were not migrated, contact QA team and coordinate fix.
* If those are not updated, there was an error made during preparation for new stable release. Please contact QA team and coordinate fix.
1. [ ] Upload Premium hooks tarball to SendOwl for legacy 2.4 or 2.6 branches. 1. [ ] Upload Premium hooks tarball to SendOwl for legacy 2.4 or 2.6 branches.
1. [ ] Send notifications to existing subscribers of the new version. 1. [ ] Send notifications to existing subscribers of the new version.
1. [ ] Write release email to _kea-announce_. Highlight breaking changes, if any. 1. [ ] Write release email to _kea-announce_. Highlight breaking changes, if any.
@ -212,7 +212,7 @@ Now it's time to publish the code.
## Support ## Support
1. [ ] Update tickets in case of waiting for support customers. 1. [ ] Update tickets if any support customers are waiting for the release.
## QA ## QA