[Git][tpo/applications/tor-browser-build][main] Update release prep issue templates - tor-commits

18 Nov 2024


      morgan pushed to branch main at The Tor Project / Applications / tor-browser-build
Commits:
4c1be3be by Morgan at 2024-11-18T22:17:10+00:00
Update release prep issue templates
- added directions on using the ./tools/browser/sign-tag script
- removed some extraneous checkboxes
- made Run: directives consistent
- fixed some typos
- - - - -
5 changed files:
- .gitlab/issue_templates/Release Prep - Mullvad Browser Alpha.md
- .gitlab/issue_templates/Release Prep - Mullvad Browser Stable.md
- .gitlab/issue_templates/Release Prep - Tor Browser Alpha.md
- .gitlab/issue_templates/Release Prep - Tor Browser Legacy.md
- .gitlab/issue_templates/Release Prep - Tor Browser Stable.md
Changes:
=====================================
.gitlab/issue_templates/Release Prep - Mullvad Browser Alpha.md
=====================================
@@ -41,13 +41,17 @@
- [ ] Tag `mullvad-browser` commit:
   - **example**: `mullvad-browser-128.4.0esr-14.5-1-build1`
+  - Run:
+    ```bash
+    ./tools/browser/sign-tag.mullvadbrowser alpha ${BUILD_N}
+    ```
### tor-browser-build: https://gitlab.torproject.org/tpo/applications/tor-browser-build.git
 Mullvad Browser Alpha (and Nightly) are on the `main` branch
- [ ] Changelog bookkeeping:
-  - [ ] Ensure all commits to `mullvad-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
-  - [ ] Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
+  - Ensure all commits to `mullvad-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
+  - Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
 - [ ] Create a release preparation branch from the `main` branch
 - [ ] Run release preparation script:
   - **NOTE**: You can omit the `--mullvad-browser` argument if this is for a joint Tor and Mullvad Browser release
@@ -71,24 +75,24 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
     - [ ] `steps/base-browser/git_hash`: updated with `HEAD` commit of project's `base-browser` branch
     - [ ] `steps/mullvad-browser/git_hash`: updated with `HEAD` commit of project's `mullvad-browser` branch
   - [ ] ***(Optional)*** `projects/browser/config`:
-    - [ ] NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
+    - [ ] ***(Optional)***  NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
       - [ ] `URL` updated
         - **⚠️ WARNING**: If preparing the release manually, updating the version number in the url is not sufficient, as each version has a random unique id in the download url
       - [ ] `sha256sum` updated
-    - [ ] uBlock-origin: https://addons.mozilla.org/en-US/firefox/addon/ublock-origin
+    - [ ] ***(Optional)*** uBlock-origin: https://addons.mozilla.org/en-US/firefox/addon/ublock-origin
       - [ ] `URL` updated
         - **⚠️ WARNING**: If preparing the release manually, updating the version number in the url is not sufficient, as each version has a random unique id in the download url
       - [ ] `sha256sum` updated
-    - [ ] Mullvad Browser extension: https://github.com/mullvad/browser-extension/releases
+    - [ ] ***(Optional)*** Mullvad Browser extension: https://github.com/mullvad/browser-extension/releases
       - [ ] `URL` updated
       - [ ] `sha256sum` updated
   - [ ] `ChangeLog-MB.txt`: ensure correctness
-    - [ ] Browser name correct
-    - [ ] Release date correct
-    - [ ] No Android updates
-    - [ ] All issues added under correct platform
-    - [ ] ESR updates correct
-    - [ ] Component updates correct
+    - Browser name correct
+    - Release date correct
+    - No Android updates
+    - All issues added under correct platform
+    - ESR updates correct
+    - Component updates correct
 - [ ] Open MR with above changes, using the template for release preparations
   - **NOTE**: target the `main` branch
 - [ ] Merge
@@ -99,13 +103,13 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
     - ma1
     - morgan
     - pierov
-  - [ ] Run:
+  - Run:
     ```bash
     make mullvadbrowser-signtag-alpha
     ```
-  - [ ] Push tag to `upstream`
+- [ ] Push tag to `upstream`
 - [ ] Build the tag:
-  - [ ] Run:
+  - Run:
     ```bash
     make mullvadbrowser-alpha && make mullvadbrowser-incrementals-alpha
     ```
@@ -113,8 +117,8 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
     - [ ] Local developer machine
   - [ ] Submit build request to Mullvad infrastructure:
     - **NOTE** this requires a devmole authentication token
-    - **NOTE** this also requires you be connected to a Swedish Mulvad VPN exit
-    - [ ] Run:
+    - **NOTE** this also requires you be connected to Gothenburg Mulvad VPN exit `se-got-wg-101`
+    - Run:
       ```bash
       make mullvadbrowser-kick-devmole-build
       ```
@@ -148,7 +152,7 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
     - `tbb_version_type`: either `alpha` for alpha releases or `release` for stable releases
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, ensure tor daemon is running with SOCKS5 proxy on the default port 9050
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, run do-all-signing script:
-  - [ ] Run:
+  - Run:
     ```bash
     cd tor-browser-build/tools/signing/ && ./do-all-signing.mullvadbrowser
     ```
@@ -162,7 +166,7 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
 ### website
 - [ ] On `staticiforme.torproject.org`, remove old release and publish new:
   - [ ] `/srv/dist-master.torproject.org/htdocs/mullvadbrowser`
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component dist.torproject.org
     ```
@@ -200,7 +204,7 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
     - Mullvad support alias: support@mullvadvpn.net
     - Rui Hildt: rui@mullvad.net
     ```
-    support@mullvadvpn.net rui@mullvad.net
+    support@mullvadvpn.net, rui@mullvad.net,
     ```
   - **Subject**
     ```
@@ -228,7 +232,7 @@ Mullvad Browser Alpha (and Nightly) are on the `main` branch
     - arch package maintainer: bootctl@gmail.com
     - nixOS package maintainer: dev@felschr.com
     ```
-    proletarius101@protonmail.com bootctl@gmail.com dev@felschr.com
+    proletarius101@protonmail.com, bootctl@gmail.com, dev@felschr.com,
     ```
   - **Subject**
     ```
=====================================
.gitlab/issue_templates/Release Prep - Mullvad Browser Stable.md
=====================================
@@ -41,13 +41,17 @@
- [ ] Tag `mullvad-browser` commit:
   - **example**: `mullvad-browser-128.3.0esr-14.0-1-build1`
+  - Run:
+    ```bash
+    ./tools/browser/sign-tag.mullvadbrowser stable ${BUILD_N}
+    ```
### tor-browser-build: https://gitlab.torproject.org/tpo/applications/tor-browser-build.git
 Mullvad Browser Stable is on the `maint-${MULLVAD_BROWSER_MAJOR}.${MULLVAD_BROWSER_MINOR}` branch
- [ ] Changelog bookkeeping:
-  - [ ] Ensure all commits to `mullvad-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
-  - [ ] Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
+  - Ensure all commits to `mullvad-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
+  - Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
 - [ ] Create a release preparation branch from the current `maint-XX.Y` branch
 - [ ] Run release preparation script:
   - **NOTE**: You can omit the `--mullvad-browser` argument if this is for a joint Tor and Mullvad Browser release
@@ -71,24 +75,24 @@ Mullvad Browser Stable is on the `maint-${MULLVAD_BROWSER_MAJOR}.${MULLVAD_BROWS
     - [ ] `steps/base-browser/git_hash`: updated with `HEAD` commit of project's `base-browser` branch
     - [ ] `steps/mullvad-browser/git_hash`: updated with `HEAD` commit of project's `mullvad-browser` branch
   - [ ] ***(Optional)*** `projects/browser/config`:
-    - [ ] NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
+    - [ ] ***(Optional)*** NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
       - [ ] `URL` updated
         - **⚠️ WARNING**: If preparing the release manually, updating the version number in the url is not sufficient, as each version has a random unique id in the download url
       - [ ] `sha256sum` updated
-    - [ ] uBlock-origin: https://addons.mozilla.org/en-US/firefox/addon/ublock-origin
+    - [ ] ***(Optional)*** uBlock-origin: https://addons.mozilla.org/en-US/firefox/addon/ublock-origin
       - [ ] `URL` updated
         - **⚠️ WARNING**: If preparing the release manually, updating the version number in the url is not sufficient, as each version has a random unique id in the download url
       - [ ] `sha256sum` updated
-    - [ ] Mullvad Browser extension: https://github.com/mullvad/browser-extension/releases
+    - [ ] ***(Optional)*** Mullvad Browser extension: https://github.com/mullvad/browser-extension/releases
       - [ ] `URL` updated
       - [ ] `sha256sum` updated
   - [ ] `ChangeLog-MB.txt`: ensure correctness
-    - [ ] Browser name correct
-    - [ ] Release date correct
-    - [ ] No Android updates
-    - [ ] All issues added under correct platform
-    - [ ] ESR updates correct
-    - [ ] Component updates correct
+    - Browser name correct
+    - Release date correct
+    - No Android updates
+    - All issues added under correct platform
+    - ESR updates correct
+    - Component updates correct
 - [ ] Open MR with above changes, using the template for release preparations
   - **NOTE**: target the `maint-14.0` branch
 - [ ] Merge
@@ -99,22 +103,22 @@ Mullvad Browser Stable is on the `maint-${MULLVAD_BROWSER_MAJOR}.${MULLVAD_BROWS
     - ma1
     - morgan
     - pierov
-  - [ ] Run:
+  - Run:
     ```bash
     make mullvadbrowser-signtag-release
     ```
-  - [ ] Push tag to `upstream`
+- [ ] Push tag to `upstream`
 - [ ] Build the tag:
-  - [ ] Run:
+  - Run:
     ```bash
     make mullvadbrowser-release && make mullvadbrowser-incrementals-release
     ```
-    - [ ] Tor Project build machine
-    - [ ] Local developer machine
+    - Tor Project build machine
+    - Local developer machine
   - [ ] Submit build request to Mullvad infrastructure:
     - **NOTE** this requires a devmole authentication token
-    - **NOTE** this also requires you be connected to a Swedish Mulvad VPN exit
-    - [ ] Run:
+    - **NOTE** this also requires you be connected to Gothenburg Mulvad VPN exit `se-got-wg-101`
+    - Run:
       ```bash
       make mullvadbrowser-kick-devmole-build
       ```
@@ -148,7 +152,7 @@ Mullvad Browser Stable is on the `maint-${MULLVAD_BROWSER_MAJOR}.${MULLVAD_BROWS
     - `tbb_version_type`: either `alpha` for alpha releases or `release` for stable releases
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, ensure tor daemon is running with SOCKS5 proxy on the default port 9050
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, run do-all-signing script:
-  - [ ] Run:
+  - Run:
     ```bash
     cd tor-browser-build/tools/signing/ && ./do-all-signing.mullvadbrowser
     ```
@@ -162,7 +166,7 @@ Mullvad Browser Stable is on the `maint-${MULLVAD_BROWSER_MAJOR}.${MULLVAD_BROWS
 ### website
 - [ ] On `staticiforme.torproject.org`, remove old release and publish new:
   - [ ] `/srv/dist-master.torproject.org/htdocs/mullvadbrowser`
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component dist.torproject.org
     ```
@@ -200,7 +204,7 @@ Mullvad Browser Stable is on the `maint-${MULLVAD_BROWSER_MAJOR}.${MULLVAD_BROWS
     - Mullvad support alias: support@mullvadvpn.net
     - Rui Hildt: rui@mullvad.net
     ```
-    support@mullvadvpn.net rui@mullvad.net
+    support@mullvadvpn.net, rui@mullvad.net
     ```
   - **Subject**
     ```
@@ -227,7 +231,7 @@ Mullvad Browser Stable is on the `maint-${MULLVAD_BROWSER_MAJOR}.${MULLVAD_BROWS
     - arch package maintainer: bootctl@gmail.com
     - nixOS package maintainer: dev@felschr.com
     ```
-    proletarius101@protonmail.com bootctl@gmail.com dev@felschr.com
+    proletarius101@protonmail.com, bootctl@gmail.com, dev@felschr.com,
     ```
   - **Subject**
     ```
=====================================
.gitlab/issue_templates/Release Prep - Tor Browser Alpha.md
=====================================
@@ -41,13 +41,17 @@
- [ ] Tag `tor-browser` in tor-browser.git
   - **example**: `tor-browser-128.4.0esr-14.5-1-build1`
+  - Run:
+    ```bash
+    ./tools/browser/sign-tag.torbrowser alpha ${BUILD_N}
+    ```
### tor-browser-build: https://gitlab.torproject.org/tpo/applications/tor-browser-build.git
 Tor Browser Alpha (and Nightly) are on the `main` branch
- [ ] Changelog bookkeeping:
-  - [ ] Ensure all commits to `tor-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
-  - [ ] Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Android, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
+  - Ensure all commits to `tor-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
+  - Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Android, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
 - [ ] Create a release preparation branch from the `main` branch
 - [ ] Run release preparation script:
   - **NOTE**: You can omit the `--tor-browser` argument if this is for a jointt Tor and Mullvad Browser release
@@ -75,7 +79,7 @@ Tor Browser Alpha (and Nightly) are on the `main` branch
     - [ ] `steps/tor-browser/git_hash`: updated with `HEAD` commit of project's `tor-browser` branch
     - [ ] `steps/fenix/git_hash`: updated with `HEAD` commit of project's `fenix-torbrowserstringsxml` branch
   - [ ] ***(Optional)*** `projects/browser/config`:
-    - [ ] NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
+    - [ ] ***(Optional)*** NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
       - [ ] `URL` updated
         - **⚠️ WARNING**: If preparing the release manually, updating the version number in the url is not sufficient, as each version has a random unique id in the download url
       - [ ] `sha256sum` updated
@@ -101,18 +105,18 @@ Tor Browser Alpha (and Nightly) are on the `main` branch
     - [ ] `input_files/shasum` for `manual`: updated to manual hash
     - [ ] Upload the downloaded `manual_${PIPELINEID}.zip` file to `tb-build-02.torproject.org`
     - [ ] Deploy to `tb-builder`'s `public_html` directory:
-      - [ ] Run:
+      - Run:
         ```bash
         sudo -u tb-builder cp manual_${PIPELINEID}.zip ~tb-builder/public_html/.
         ```
       - `sudo` documentation for TPO machines: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/doc/accounts#changingrese...
   - [ ] `ChangeLog-TBB.txt`: ensure correctness
-    - [ ] Browser name correct
-    - [ ] Release date correct
-    - [ ] No Android updates on a desktop-only release and vice-versa
-    - [ ] All issues added under correct platform
-    - [ ] ESR updates correct
-    - [ ] Component updates correct
+    - Browser name correct
+    - Release date correct
+    - No Android updates on a desktop-only release and vice-versa
+    - All issues added under correct platform
+    - ESR updates correct
+    - Component updates correct
 - [ ] Open MR with above changes, using the template for release preparations
   - **NOTE**: target the `main` branch
 - [ ] Merge
@@ -123,13 +127,13 @@ Tor Browser Alpha (and Nightly) are on the `main` branch
     - ma1
     - morgan
     - pierov
-  - [ ] Run:
+  - Run:
     ```bash
     make torbrowser-signtag-alpha
     ```
-  - [ ] Push tag to `upstream`
+- [ ] Push tag to `upstream`
 - [ ] Build the tag:
-  - [ ] Run:
+  - Run:
     ```bash
     make torbrowser-alpha && make torbrowser-incrementals-alpha
     ```
@@ -137,8 +141,8 @@ Tor Browser Alpha (and Nightly) are on the `main` branch
     - [ ] Local developer machine
   - [ ] Submit build request to Mullvad infrastructure:
     - **NOTE** this requires a devmole authentication token
-    - **NOTE** this also requires you be connected to a Swedish Mulvad VPN exit
-    - [ ] Run:
+    - **NOTE** this also requires you be connected to Gothenburg Mulvad VPN exit `se-got-wg-101`
+    - Run:
       ```bash
       make torbrowser-kick-devmole-build
       ```
@@ -160,9 +164,14 @@ Tor Browser Alpha (and Nightly) are on the `main` branch
     - **⚠️ WARNING**: Do not deploy yet!
### blog: https://gitlab.torproject.org/tpo/web/blog.git
-  - [ ] Run `tools/signing/create-blog-post` which should create the new blog post from a template (edit set-config.blog to set you local blog directory)
-    - [ ] Note any ESR update
-    - [ ] Thank any users which have contributed patches
+  - [ ] Generate release blog post
+    - Run:
+    ```bash
+    ./tools/signing/create-blog-post.torbrowser
+    ```
+    - **NOTE** this script creates the new blog post from a template (edit `./tools/signing/set-config.blog` to set you local blog directory)
+    - [ ] **(Optional)** Note any ESR update
+    - [ ] **(Optional)** Thank any users which have contributed patches
     - [ ] **(Optional)** Draft any additional sections for new features which need testing, known issues, etc
   - [ ] Push to origin as new branch and open MR
   - [ ] Review
@@ -198,7 +207,7 @@ Tor Browser Alpha (and Nightly) are on the `main` branch
     - `tbb_version_type`: either `alpha` for alpha releases or `release` for stable releases
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, ensure tor daemon is running with SOCKS5 proxy on the default port 9050
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, run do-all-signing script:
-  - [ ] Run:
+  - Run:
     ```bash
     cd tor-browser-build/tools/signing/ && ./do-all-signing.torbrowser
     ```
@@ -244,14 +253,14 @@ popd
### website
 - [ ] On `staticiforme.torproject.org`, static update components:
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component cdn.torproject.org && static-update-component dist.torproject.org
     ```
 - [ ] Deploy `tor-website` MR
 - [ ] Deploy `tor-blog` MR
 - [ ] On `staticiforme.torproject.org`, enable update responses:
-  - [ ] Run:
+  - Run:
     ```bash
     sudo -u tb-release ./deploy_update_responses-alpha.sh
     ```
@@ -259,7 +268,7 @@ popd
   - **NOTE**: Skip this step if we need to hold on to older versions for some reason (for example, this is an Andoid or Desktop-only release, or if we need to hold back installers in favor of build-to-build updates if there are signing issues, etc)
   - [ ] `/srv/cdn-master.torproject.org/htdocs/aus1/torbrowser`
   - [ ] `/srv/dist-master.torproject.org/htdocs/torbrowser`
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component cdn.torproject.org && static-update-component dist.torproject.org
     ```
@@ -314,7 +323,7 @@ popd
     - torbrowser-launcher: mail@asciiwolf.com <!-- Gitlab user asciiwolf -->
     - Anti-Censorship: meskio@torproject.org <!-- Gitlab user meskio -->
     ```
-    tails-dev@boum.org nathan@guardianproject.info freebsd@sysctl.cz caspar@schutijser.com mail@asciiwolf.com meskio@torproject.org
+    tails-dev@boum.org, nathan@guardianproject.info, freebsd@sysctl.cz, caspar@schutijser.com, mail@asciiwolf.com, meskio@torproject.org,
     ```
   - **Subject**
     ```
=====================================
.gitlab/issue_templates/Release Prep - Tor Browser Legacy.md
=====================================
@@ -40,13 +40,17 @@
- [ ] Tag `tor-browser` in tor-browser.git
   - **example**: `tor-browser-115.17.0esr-13.5-1-build1`
+  - Run:
+    ```bash
+    ./tools/browser/sign-tag.torbrowser legacy ${BUILD_N}
+    ```
### tor-browser-build: https://gitlab.torproject.org/tpo/applications/tor-browser-build.git
 Tor Browser Legacy is on the `maint-13.5` branch
- [ ] Changelog bookkeeping:
-  - [ ] Ensure all commits to `tor-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
-  - [ ] Ensure each issue has a platform (~Windows, ~MacOS, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
+  - Ensure all commits to `tor-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
+  - Ensure each issue has a platform (~Windows, ~MacOS, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
 - [ ] Create a release preparation branch from the `maint-13.5` branch
 - [ ] Run release preparation script:
   - **⚠️ WARNING**: You may need to manually update the `firefox/config` file's `browser_build` field if `tor-browser.git` has not yet been tagged (e.g. if security backports have not yet been merged and tagged)
@@ -69,7 +73,7 @@ Tor Browser Legacy is on the `maint-13.5` branch
     - [ ] `steps/base-browser/git_hash`: updated with `HEAD` commit of project's `base-browser` branch
     - [ ] `steps/tor-browser/git_hash`: updated with `HEAD` commit of project's `tor-browser` branch
   - [ ] ***(Optional)*** `projects/browser/config`:
-    - [ ] NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
+    - [ ] ***(Optional)*** NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
       - [ ] `URL` updated
         - **⚠️ WARNING**: If preparing the release manually, updating the version number in the url is not sufficient, as each version has a random unique id in the download url
       - [ ] `sha256sum` updated
@@ -94,18 +98,18 @@ Tor Browser Legacy is on the `maint-13.5` branch
     - [ ] `input_files/shasum` for `manual`: updated to manual hash
     - [ ] Upload the downloaded `manual_${PIPELINEID}.zip` file to `tb-build-02.torproject.org`
     - [ ] Deploy to `tb-builder`'s `public_html` directory:
-      - [ ] Run:
+      - Run:
         ```bash
         sudo -u tb-builder cp manual_${PIPELINEID}.zip ~tb-builder/public_html/.
         ```
       - `sudo` documentation for TPO machines: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/doc/accounts#changingrese...
   - [ ] `ChangeLog-TBB.txt`: ensure correctness
-    - [ ] Browser name correct
-    - [ ] Release date correct
-    - [ ] No Android updates
-    - [ ] All issues added under correct platform
-    - [ ] ESR updates correct
-    - [ ] Component updates correct
+    - Browser name correct
+    - Release date correct
+    - No Android updates
+    - All issues added under correct platform
+    - ESR updates correct
+    - Component updates correct
 - [ ] Open MR with above changes, using the template for release preparations
   - **NOTE**: target the `maint-13.5` branch
 - [ ] Merge
@@ -116,13 +120,13 @@ Tor Browser Legacy is on the `maint-13.5` branch
     - ma1
     - morgan
     - pierov
-  - [ ] Run:
+  - Run:
     ```bash
     make torbrowser-signtag-release
     ```
-  - [ ] Push tag to `upstream`
+- [ ] Push tag to `upstream`
 - [ ] Build the tag:
-  - [ ] Run:
+  - Run:
     ```bash
     make torbrowser-release && make torbrowser-incrementals-release
     ```
@@ -130,8 +134,8 @@ Tor Browser Legacy is on the `maint-13.5` branch
     - [ ] Local developer machine
   - [ ] Submit build request to Mullvad infrastructure:
     - **NOTE** this requires a devmole authentication token
-    - **NOTE** this also requires you be connected to a Swedish Mulvad VPN exit
-    - [ ] Run:
+    - **NOTE** this also requires you be connected to Gothenburg Mulvad VPN exit `se-got-wg-101`
+    - Run:
       ```bash
       make torbrowser-kick-devmole-build
       ```
@@ -142,9 +146,14 @@ Tor Browser Legacy is on the `maint-13.5` branch
   <summary>Website</summary>
### blog: https://gitlab.torproject.org/tpo/web/blog.git
-  - [ ] Run `tools/signing/create-blog-post` which should create the new blog post from a template (edit set-config.blog to set you local blog directory)
-    - [ ] Note any ESR update
-    - [ ] Thank any users which have contributed patches
+  - [ ] Generate release blog post
+    - Run:
+    ```bash
+    ./tools/signing/create-blog-post.torbrowser
+    ```
+    - **NOTE** this script creates the new blog post from a template (edit `./tools/signing/set-config.blog` to set you local blog directory)
+    - [ ] **(Optional)** Note any ESR update
+    - [ ] **(Optional)** Thank any users which have contributed patches
     - [ ] **(Optional)** Draft any additional sections for new features which need testing, known issues, etc
   - [ ] Push to origin as new branch and open MR
   - [ ] Review
@@ -178,7 +187,7 @@ Tor Browser Legacy is on the `maint-13.5` branch
     - `tbb_version_type`: either `alpha` for alpha releases or `release` for stable releases
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, ensure tor daemon is running with SOCKS5 proxy on the default port 9050
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, run do-all-signing script:
-  - [ ] Run:
+  - Run:
     ```bash
     cd tor-browser-build/tools/signing/ && ./do-all-signing.torbrowser
     ```
@@ -224,7 +233,7 @@ popd
### website
 - [ ] On `staticiforme.torproject.org`, static update components:
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component cdn.torproject.org && static-update-component dist.torproject.org
     ```
@@ -233,7 +242,7 @@ popd
   - **NOTE**: Skip this step if we need to hold on to older versions for some reason (for example, this is an Andoid or Desktop-only release, or if we need to hold back installers in favor of build-to-build updates if there are signing issues, etc)
   - [ ] `/srv/cdn-master.torproject.org/htdocs/aus1/torbrowser`
   - [ ] `/srv/dist-master.torproject.org/htdocs/torbrowser`
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component cdn.torproject.org && static-update-component dist.torproject.org
     ```
@@ -247,12 +256,12 @@ popd
       - [ ] `var/torbrowser_legacy_platform_version`: update to `${ESR_VERSION}`
         - **NOTE** this is ESR version for the legacy branch, not the 14.0 branch
     - [ ] Generate update responses:
-      - [ ] Run:
+      - Run:
         ```bash
         make torbrowser-update_responses-release
         ```
     - [ ] Commit new update responses to tor-browser-update-responses.git:
-      - [ ] Run:
+      - Run:
         ```bash
         updaterespdir=/path/to/tor-browser-update-responses.git
         cp torbrowser/release/update-responses/update-responses-release-${TOR_BROWSER_VERSION}.tar "$updaterespdir"
=====================================
.gitlab/issue_templates/Release Prep - Tor Browser Stable.md
=====================================
@@ -41,13 +41,17 @@
- [ ] Tag `tor-browser` in tor-browser.git
   - **example**: `tor-browser-128.4.0esr-14.0-1-build1`
+  - Run:
+    ```bash
+    ./tools/browser/sign-tag.torbrowser stable ${BUILD_N}
+    ```
### tor-browser-build: https://gitlab.torproject.org/tpo/applications/tor-browser-build.git
 Tor Browser Stable is on the `maint-${TOR_BROWSER_MAJOR}.${TOR_BROWSER_MINOR}` branch
- [ ] Changelog bookkeeping:
-  - [ ] Ensure all commits to `tor-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
-  - [ ] Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Android, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
+  - Ensure all commits to `tor-browser` and `tor-browser-build` for this release have an associated issue linked to this release preparation issue
+  - Ensure each issue has a platform (~Windows, ~MacOS, ~Linux, ~Android, ~Desktop, ~"All Platforms") and potentially ~"Build System" labels
 - [ ] Create a release preparation branch from the current `maint-XX.Y` branch
 - [ ] Run release preparation script:
   - **NOTE**: You can omit the `--tor-browser` argument if this is for a joint Tor and Mullvad Browser release
@@ -64,9 +68,9 @@ Tor Browser Stable is on the `maint-${TOR_BROWSER_MAJOR}.${TOR_BROWSER_MINOR}` b
     - [ ] ***(Desktop Only)*** `var/torbrowser_incremental_from`: updated to previous Desktop version
       - **NOTE**: We try to build incrementals for the previous 3 desktop versions
       - **⚠️ WARNING**: Really *actually* make sure this is the previous Desktop version or else the `make torbrowser-incrementals-*` step will fail
-- [ ] `projects/firefox/config`
-    - [ ] `browser_build`: updated to match `tor-browser` tag
-    - [ ] ***(Optional)*** `var/firefox_platform_version`: updated to latest `${ESR_VERSION}` if rebased
+  - [ ] `projects/firefox/config`
+      - [ ] `browser_build`: updated to match `tor-browser` tag
+      - [ ] ***(Optional)*** `var/firefox_platform_version`: updated to latest `${ESR_VERSION}` if rebased
   - [ ] `projects/geckoview/config`
     - [ ] `browser_build`: updated to match `tor-browser` tag
     - [ ] ***(Optional)*** `var/firefox_platform_version`: updated to latest `${ESR_VERSION}` if rebased
@@ -75,7 +79,7 @@ Tor Browser Stable is on the `maint-${TOR_BROWSER_MAJOR}.${TOR_BROWSER_MINOR}` b
     - [ ] `steps/tor-browser/git_hash`: updated with `HEAD` commit of project's `tor-browser` branch
     - [ ] `steps/fenix/git_hash`: updated with `HEAD` commit of project's `fenix-torbrowserstringsxml` branch
   - [ ] ***(Optional)*** `projects/browser/config`:
-    - [ ] NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
+    - [ ] ***(Optional)*** NoScript: https://addons.mozilla.org/en-US/firefox/addon/noscript
       - [ ] `URL` updated
         - **⚠️ WARNING**: If preparing the release manually, updating the version number in the url is not sufficient, as each version has a random unique id in the download url
       - [ ] `sha256sum` updated
@@ -101,18 +105,18 @@ Tor Browser Stable is on the `maint-${TOR_BROWSER_MAJOR}.${TOR_BROWSER_MINOR}` b
     - [ ] `input_files/shasum` for `manual`: updated to manual hash
     - [ ] Upload the downloaded `manual_${PIPELINEID}.zip` file to `tb-build-02.torproject.org`
     - [ ] Deploy to `tb-builder`'s `public_html` directory:
-      - [ ] Run:
+      - Run:
         ```bash
         sudo -u tb-builder cp manual_${PIPELINEID}.zip ~tb-builder/public_html/.
         ```
       - `sudo` documentation for TPO machines: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/doc/accounts#changingrese...
   - [ ] `ChangeLog-TBB.txt`: ensure correctness
-    - [ ] Browser name correct
-    - [ ] Release date correct
-    - [ ] No Android updates on a desktop-only release and vice-versa
-    - [ ] All issues added under correct platform
-    - [ ] ESR updates correct
-    - [ ] Component updates correct
+    - Browser name correct
+    - Release date correct
+    - No Android updates on a desktop-only release and vice-versa
+    - All issues added under correct platform
+    - ESR updates correct
+    - Component updates correct
 - [ ] Open MR with above changes, using the template for release preparations
   - **NOTE**: target the `maint-14.0` branch
 - [ ] Merge
@@ -123,22 +127,22 @@ Tor Browser Stable is on the `maint-${TOR_BROWSER_MAJOR}.${TOR_BROWSER_MINOR}` b
     - ma1
     - morgan
     - pierov
-  - [ ] Run:
+  - Run:
     ```bash
     make torbrowser-signtag-release
     ```
-  - [ ] Push tag to `upstream`
+- [ ] Push tag to `upstream`
 - [ ] Build the tag:
-  - [ ] Run:
+  - Run:
     ```bash
     make torbrowser-release && make torbrowser-incrementals-release
     ```
-    - [ ] Tor Project build machine
-    - [ ] Local developer machine
+    - Tor Project build machine
+    - Local developer machine
   - [ ] Submit build request to Mullvad infrastructure:
     - **NOTE** this requires a devmole authentication token
-    - **NOTE** this also requires you be connected to a Swedish Mulvad VPN exit
-    - [ ] Run:
+    - **NOTE** this also requires you be connected to Gothenburg Mulvad VPN exit `se-got-wg-101`
+    - Run:
       ```bash
       make torbrowser-kick-devmole-build
       ```
@@ -160,9 +164,14 @@ Tor Browser Stable is on the `maint-${TOR_BROWSER_MAJOR}.${TOR_BROWSER_MINOR}` b
     - **⚠️ WARNING**: Do not deploy yet!
### blog: https://gitlab.torproject.org/tpo/web/blog.git
-  - [ ] Run `tools/signing/create-blog-post` which should create the new blog post from a template (edit set-config.blog to set you local blog directory)
-    - [ ] Note any ESR update
-    - [ ] Thank any users which have contributed patches
+  - [ ] Generate release blog post
+    - Run:
+    ```bash
+    ./tools/signing/create-blog-post.torbrowser
+    ```
+    - **NOTE** this script creates the new blog post from a template (edit `./tools/signing/set-config.blog` to set you local blog directory)
+    - [ ] **(Optional)** Note any ESR update
+    - [ ] **(Optional)** Thank any users which have contributed patches
     - [ ] **(Optional)** Draft any additional sections for new features which need testing, known issues, etc
   - [ ] Push to origin as new branch and open MR
   - [ ] Review
@@ -201,7 +210,7 @@ Tor Browser Stable is on the `maint-${TOR_BROWSER_MAJOR}.${TOR_BROWSER_MINOR}` b
     - `tbb_version_type`: either `alpha` for alpha releases or `release` for stable releases
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, ensure tor daemon is running with SOCKS5 proxy on the default port 9050
 - [ ] On `${STAGING_SERVER}` in a separate `screen` session, run do-all-signing script:
-  - [ ] Run:
+  - Run:
     ```bash
     cd tor-browser-build/tools/signing/ && ./do-all-signing.torbrowser
     ```
@@ -247,14 +256,14 @@ popd
### website
 - [ ] On `staticiforme.torproject.org`, static update components:
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component cdn.torproject.org && static-update-component dist.torproject.org
     ```
 - [ ] Deploy `tor-website` MR
 - [ ] Deploy `tor-blog` MR
 - [ ] On `staticiforme.torproject.org`, enable update responses:
-  - [ ] Run:
+  - Run:
     ```bash
     sudo -u tb-release ./deploy_update_responses-release.sh
     ```
@@ -262,7 +271,7 @@ popd
   - **NOTE**: Skip this step if we need to hold on to older versions for some reason (for example, this is an Andoid or Desktop-only release, or if we need to hold back installers in favor of build-to-build updates if there are signing issues, etc)
   - [ ] `/srv/cdn-master.torproject.org/htdocs/aus1/torbrowser`
   - [ ] `/srv/dist-master.torproject.org/htdocs/torbrowser`
-  - [ ] Run:
+  - Run:
     ```bash
     static-update-component cdn.torproject.org && static-update-component dist.torproject.org
     ```
@@ -317,7 +326,7 @@ popd
     - torbrowser-launcher: mail@asciiwolf.com <!-- Gitlab user asciiwolf -->
     - Anti-Censorship: meskio@torproject.org <!-- Gitlab user meskio -->
     ```
-    tails-dev@boum.org nathan@guardianproject.info freebsd@sysctl.cz caspar@schutijser.com mail@asciiwolf.com meskio@torproject.org
+    tails-dev@boum.org, nathan@guardianproject.info, freebsd@sysctl.cz, caspar@schutijser.com, mail@asciiwolf.com, meskio@torproject.org,
     ```
   - **Subject**
     ```
View it on GitLab: https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/commit/4c...
-- 
View it on GitLab: https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/commit/4c...
You're receiving this email because of your account on gitlab.torproject.org.





    