From 99b8ebab557276e08a551e9b37cfa84449832552 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dylan=20A=C3=AFssi?= <dylan.aissi@collabora.com> Date: Mon, 16 Sep 2024 16:21:14 +0200 Subject: [PATCH] Apertis release process: add recommendation to update the dashboard MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com> --- .../guides/maintenance/apertis_release_process.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/content/guides/maintenance/apertis_release_process.md b/content/guides/maintenance/apertis_release_process.md index 505b3468a..6bd3fcf19 100644 --- a/content/guides/maintenance/apertis_release_process.md +++ b/content/guides/maintenance/apertis_release_process.md @@ -54,6 +54,7 @@ As a high level overview, these are the steps to be executed during the release * Check available [disk space on OBS Server](#obs-disk-space) * Perform [Release Branching](#release-branching) * [Publish Release](#publish-release) +* Update channels for [Apertis packages Dashboard](#dashboard-update) ## Release Branching @@ -144,6 +145,7 @@ A Stable Point Release includes: * [Publish Release Candidate](#publish-release-candidate) (RC1) images and announce hard code freeze * RC images validation (QA) * [Publish Release](#publish-release) +* Update channels for [Apertis packages Dashboard](#dashboard-update) Several of the steps above were already described in the previous section, the following section will describe those steps specific for stable point releases. @@ -472,3 +474,15 @@ obsolete *Beta* and *Preview* distribution releases, like: `v2019dev0`, `v2019pr Deleting vanished identifier 'u|v2019pre|proprietary|amd64'. Deleting vanished identifier 'u|v2019pre|proprietary|armhf'. ``` + +## Dashboard update + +At the end of the release process, it's necessary to update the channels tracked +by the [Apertis packages Dashboard](https://infrastructure.pages.apertis.org/dashboard/). +This ensures that we focus on current releases. +As soon as we publish a new release, it can be marked as closed (with `status: closed`) +in the [channels.yaml](https://gitlab.apertis.org/infrastructure/dashboard/-/blob/master/data/channels.yaml), +this will hide some reports which are no longer of interest. +Two weeks after a release, it can be completely removed from this channels file. +This period allows us to keep an eye on a release after its publication in case +of potential issues while downstream projects are synchronizing. -- GitLab