From cb26bdca4546d453fb3a1dc9c501bb1c1262c1a8 Mon Sep 17 00:00:00 2001 From: Remy Haemmerle Date: Thu, 4 Sep 2025 15:09:52 +0200 Subject: [PATCH 1/3] Add weekly snapshot verification step to release/README.md to check the component are not outdated. --- sdk/release/RELEASE.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/sdk/release/RELEASE.md b/sdk/release/RELEASE.md index c087ad7ff4db..d711e33429a4 100644 --- a/sdk/release/RELEASE.md +++ b/sdk/release/RELEASE.md @@ -74,6 +74,15 @@ using the steps in the previous section. ## Testing +For the weekly snapshot of the main branch, before merging the +assembly PR, verify that the SDK snapshot used in the release is not +older than one week. If it is outdated, open a #team-daml thread +tagging @martino, @Raf, @soren, and @Tom Tantillo, stating that the +release will be skipped this week unless instructed otherwise. Then, +close the two automatically generated PRs (one in the assembly repo +and the rotate release duty PR in the SDK repo) and halt the testing +process. + This testing procedure starts once the release is listed on the [releases page]. That is, _after_ the [assembly] step has finished. From 2a1056d502260d469b0e99eedf11a74d4f303d03 Mon Sep 17 00:00:00 2001 From: Remy Haemmerle Date: Thu, 4 Sep 2025 15:31:50 +0200 Subject: [PATCH 2/3] address Fabio review --- sdk/release/RELEASE.md | 27 +++++++++++++++++---------- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/sdk/release/RELEASE.md b/sdk/release/RELEASE.md index d711e33429a4..26e6232678cd 100644 --- a/sdk/release/RELEASE.md +++ b/sdk/release/RELEASE.md @@ -33,7 +33,7 @@ The steps to create a release are: of the release branch), the version number you want to attribute to the build, and the words `SPLIT_RELEASE` (for historical reason dating to pre-2.0 days). For a snapshot release, one can generate a snapshot version - string using the `release.sh` script. For example, to create a PR for a + string using the `release.sh` script. For example, to create a PR for a 2.0.0 snapshot release: ``` @@ -76,15 +76,22 @@ using the steps in the previous section. For the weekly snapshot of the main branch, before merging the assembly PR, verify that the SDK snapshot used in the release is not -older than one week. If it is outdated, open a #team-daml thread -tagging @martino, @Raf, @soren, and @Tom Tantillo, stating that the -release will be skipped this week unless instructed otherwise. Then, -close the two automatically generated PRs (one in the assembly repo -and the rotate release duty PR in the SDK repo) and halt the testing -process. - -This testing procedure starts once the release is listed on the [releases -page]. That is, _after_ the [assembly] step has finished. +older than one week. If it is outdated, post the following message in +the #team-daml Slack thread created one by the assembly repo process: + +``` +At least one component of the automatically generated release is more +than one week old. Unless instructed otherwise, we will skip the +release this week. cc @martino, @Raf, @soren, @Tom Tantillo, @Rémy +``` + +Then, close the two automatically generated PRs (one in the assembly +repo and the rotate release duty PR in the SDK repo) and halt the +release testing process. + +The following of the testing procedure starts once the release is +listed on the [releases page]. That is, _after_ the [assembly] step +has finished. In the following notes, we assume that `$VERSION` contains the full version tag for the release you are testing - in other words, the full version as recorded From ff3c5098c2ebd39fbb7b23f4eefa95248b85788f Mon Sep 17 00:00:00 2001 From: Remy Haemmerle Date: Thu, 4 Sep 2025 15:32:43 +0200 Subject: [PATCH 3/3] cosmetic --- sdk/release/RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdk/release/RELEASE.md b/sdk/release/RELEASE.md index 26e6232678cd..4d63ce8837ef 100644 --- a/sdk/release/RELEASE.md +++ b/sdk/release/RELEASE.md @@ -33,7 +33,7 @@ The steps to create a release are: of the release branch), the version number you want to attribute to the build, and the words `SPLIT_RELEASE` (for historical reason dating to pre-2.0 days). For a snapshot release, one can generate a snapshot version - string using the `release.sh` script. For example, to create a PR for a + string using the `release.sh` script. For example, to create a PR for a 2.0.0 snapshot release: ```