Reassign release (pre-)publishing to QA

diff --git a/.gitlab/issue_templates/Release.md b/.gitlab/issue_templates/Release.md
index decacbd3d71a48f1bede95fc7f017dee89ea3f3b..b4b3f93962858f9c47a8d53083e9e7ab8f250271 100644 (file)
--- a/.gitlab/issue_templates/Release.md
+++ b/.gitlab/issue_templates/Release.md
@@ -64,18 +64,17 @@
  - [ ] ***(Signers)*** Validate tarball checksums, sign tarballs, and upload signatures.
  - [ ] ***(QA)*** Verify tarball signatures and check tarball checksums again: Run `publish_bind.sh` on repo.isc.org to pre-publish.
  - [ ] ***(QA)*** Prepare the `patches/` subdirectory for each security release (if applicable).
- - [ ] ***(Support)*** Pre-publish ASN and/or Subscription Edition tarballs so that packages can be built.
+ - [ ] ***(QA)*** Pre-publish ASN and/or Subscription Edition tarballs so that packages can be built.
  - [ ] ***(QA)*** Build and test ASN and/or Subscription Edition packages (in [cloudsmith branch in private repo](https://gitlab.isc.org/isc-private/rpms/bind/-/tree/cloudsmith)). [Example](https://gitlab.isc.org/isc-private/rpms/bind/-/commit/e2512f4cfaf991827a635e374e7e93b27a5f38ba)
- - [ ] ***(QA)*** Notify Support that the releases have been prepared.
  - [ ] ***(QA)*** Use the [Printing Press project](https://gitlab.isc.org/isc-private/printing-press/-/wikis/home#adding-new-documents) to prepare a release announcement email.
  - [ ] ***(Marketing)*** Update ASN documents in the SF portal.
  - [ ] ***(Marketing)*** Send out ASN emails (if applicable).
 
 ### On the Day of Public Release
 
- - [ ] ***(Support)*** Wait for clearance from Security Officer to proceed with the public release (if applicable).
- - [ ] ***(Support)*** Place tarballs in public location on FTP site.
- - [ ] ***(Support)*** Inform Marketing of the release, providing FTP links for the published tarballs.
+ - [ ] ***(QA)*** Wait for clearance from Security Officer to proceed with the public release (if applicable).
+ - [ ] ***(QA)*** Place tarballs in public location on FTP site.
+ - [ ] ***(QA)*** Inform Marketing of the release, providing FTP links for the published tarballs.
  - [ ] ***(Marketing)*** Publish links to downloads on ISC website. [Example](https://gitlab.isc.org/website/theme-staging-site/-/commit/1ac7b30b73cb03228df4cd5651fa4e774ac35625)
  - [ ] ***(Marketing)*** Update the BIND -S information document in SF with download links to the new versions. (If this is a security release, this will have already been done as part of the ASN process.)
  - [ ] ***(Marketing)*** Update the Current Software Versions document in the SF portal if any stable versions were released.