From c739ed2472df88312b6580107eb26603aba73c66 Mon Sep 17 00:00:00 2001 From: George Karr Date: Tue, 26 Mar 2024 12:02:09 -0500 Subject: [PATCH] Update Releasing-Fleet.md (#16725) Updating broken link --------- Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com> --- docs/Contributing/Releasing-Fleet.md | 2 +- handbook/engineering/README.md | 1 + website/config/custom.js | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/Contributing/Releasing-Fleet.md b/docs/Contributing/Releasing-Fleet.md index c75d9c25d..f3f928fc8 100644 --- a/docs/Contributing/Releasing-Fleet.md +++ b/docs/Contributing/Releasing-Fleet.md @@ -113,7 +113,7 @@ When the Actions Workflow has been completed, [publish the new version of Fleet] 2. Check the [Docker Publish GitHub action](https://github.com/fleetdm/fleet/actions/workflows/goreleaser-snapshot-fleet.yaml) to confirm it completes successfully for this branch. -3. Create a [Release QA](https://github.com/fleetdm/fleet/blob/main/.github/ISSUE_TEMPLATE/smoke-tests.md) issue. Populate the version and browsers, and assign to the QA person leading the release. Add the appropriate [product group label](https://fleetdm.com/handbook/company/product-groups), and `:release` label, so that it appears on the product group's release board. +3. Create a [Release QA](https://github.com/fleetdm/fleet/blob/main/.github/ISSUE_TEMPLATE/release-qa.md) issue. Populate the version and browsers, and assign to the QA person leading the release. Add the appropriate [product group label](https://fleetdm.com/handbook/company/product-groups), and `:release` label, so that it appears on the product group's release board. 4. Notify QA that the release candidate is ready for (release QA)[#complete-release-qa]. diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 833e9af80..b8d649a05 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -124,6 +124,7 @@ Next, create a new GitHub issue using the [Release QA template](https://github.c The issue's template will contain validation steps for Fleet and individual `fleetd` components. Remove any instructions that do not apply to this release. + ### Indicate your product group is release-ready Once a product group completes its QA process during the freeze period, its QA lead moves the smoke testing ticket to the "Ready for release" column on their ZenHub board. They then notify the release ritual DRI by tagging them in a comment, indicating that their group is prepared for release. The release ritual DRI starts the [release process](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Releasing-Fleet.md) after all QA leads have made these updates and confirmed their readiness for release. diff --git a/website/config/custom.js b/website/config/custom.js index 099b22080..c76c7568d 100644 --- a/website/config/custom.js +++ b/website/config/custom.js @@ -258,7 +258,7 @@ module.exports.custom = { '.github/ISSUE_TEMPLATE': ['mikermcneil', 'lukeheath', 'sampfluger88'], '.github/ISSUE_TEMPLATE/bug-report.md': ['xpkoala','noahtalerman', 'lukeheath'], '.github/ISSUE_TEMPLATE/feature-request.md': ['xpkoala','noahtalerman', 'lukeheath'], - '.github/ISSUE_TEMPLATE/smoke-tests.md': ['xpkoala','lukeheath','noahtalerman', 'lukeheath'], + '.github/ISSUE_TEMPLATE/release-qa.md': ['xpkoala','lukeheath','noahtalerman', 'lukeheath'], }, confidentialGithubRepoMaintainersByPath: {// fleetdm/confidential