morgan pushed to branch tor-browser-140.2.0esr-15.0-1 at The Tor Project / Applications / Tor Browser

Commits:

11 changed files:

Changes:

  • .gitlab/issue_templates/060 Rebase - Alpha.md
    ... ... @@ -36,8 +36,8 @@
    36 36 
     - [ ] In [Repository Settings](https://gitlab.torproject.org/tpo/applications/tor-browser/-/settings/repository):
    37 37 
       - [ ] Remove previous alpha `base-browser` and `tor-browser` branch protection rules (this will prevent pushing new changes to the branches being rebased)
    38 38 
       - [ ] Create new `base-browser` and `tor-browser` branch protection rule:
    39 
    -    - **Branch**: `*-$(ESR_VERSION)esr-$(BROWSER_MAJOR).$(BROWSER_MINOR)-1*`
    40 
    -      - **Example**: `*-102.8.0esr-12.5-1*`
    39 
    +    - **Branch**: `(tor|base)-browser-$(ESR_VERSION)esr-$(BROWSER_MAJOR).$(BROWSER_MINOR)-1*`
    40 
    +      - **Example**: `(tor|base)-browser-102.8.0esr-12.5-1*`
    41 41 
         - **Allowed to merge**: `Maintainers`
    42 42 
         - **Allowed to push and merge**: `Maintainers`
    43 43 
         - **Allowed to force push**: `false`
    ... ... @@ -45,17 +45,8 @@
    45 45
    46 46 
     ### **Create New Branches**
    47 47
    48 
    -- [ ] Find the Firefox mercurial tag `$(ESR_TAG)`
    49 
    -  - If `$(BROWSER_MINOR)` is 5, the tag should already exist from the stable release
    50 
    -  - Otherwise:
    51 
    -    - [ ] Go to `https://hg.mozilla.org/releases/mozilla-esr$(ESR_MAJOR)/tags`
    52 
    -    - [ ] Find and inspect the commit tagged with `$(ESR_TAG)`
    53 
    -      - Tags are in yellow in the Mercurial web UI
    54 
    -    - [ ] Find the equivalent commit in `https://github.com/mozilla/gecko-dev/commits/esr$(ESR_MAJOR)`
    55 
    -      - The tag should be very close to `HEAD` (usually the second, before a `No bug - Tagging $(HG_HASH) with $(ESR_TAG)`)
    56 
    -      - **Notice**: GitHub sorts commits by time, you might want to use `git log gecko-dev/esr$(ESR_MAJOR)` locally, instead
    57 
    -    - [ ] Sign/Tag the `gecko-dev` commit: `git tag -as $(ESR_TAG) $(GIT_HASH) -m "Hg tag $(ESR_TAG)"`
    58 
    -- [ ] Create new alpha `base-browser` branch from Firefox mercurial tag
    48 
    +- [ ] Fetch Mozilla's firefox repo and identify this release's ${ESR_TAG}
    49 
    +- [ ] Create new alpha `base-browser` branch from Firefox ${ESR_TAG}
    59 50 
       - Branch name in the form: `base-browser-$(ESR_VERSION)esr-$(BROWSER_MAJOR).$(BROWSER_MINOR)-1`
    60 51 
       - **Example**: `base-browser-102.8.0esr-12.5-1`
    61 52 
     - [ ] Create new alpha `tor-browser` branch from Firefox mercurial tag
    ... ... @@ -160,4 +151,4 @@
    160 151
    161 152 
     /label ~"Apps::Product::TorBrowser"
    162 153 
     /label ~"Apps::Type::Rebase"
    163 
    -/label ~"Apps::Priority::Blocker"
    154 
    +/label ~"Priority::Blocker"

  • .gitlab/issue_templates/061 Rebase - Stable.md
    ... ... @@ -34,23 +34,15 @@
    34 34 
     - [ ] In [Repository Settings](https://gitlab.torproject.org/tpo/applications/tor-browser/-/settings/repository):
    35 35 
       - [ ] Remove previous stable `base-browser` and `tor-browser` branch protection rules (this will prevent pushing new changes to the branches being rebased)
    36 36 
       - [ ] Create new `base-browser` and `tor-browser` branch protection rule:
    37 
    -    - **Branch**: `*-$(ESR_VERSION)esr-$(BROWSER_MAJOR).$(BROWSER_MINOR)-1*`
    38 
    -      - **Example**: `*-102.8.0esr-12.0-1*`
    37 
    +    - **Branch**: `(tor|base)-browser-$(ESR_VERSION)esr-$(BROWSER_MAJOR).$(BROWSER_MINOR)-1*`
    38 
    +      - **Example**: `(tor|base)-browser-102.8.0esr-12.0-1*`
    39 39 
         - **Allowed to merge**: `Maintainers`
    40 40 
         - **Allowed to push and merge**: `Maintainers`
    41 41 
         - **Allowed to force push**: `false`
    42 42
    43 43 
     ### **Identify the Firefox Tagged Commit and Create New Branches**
    44 44
    45 
    -- [ ] Find the Firefox mercurial tag here: https://hg.mozilla.org/releases/mozilla-esr102/tags
    46 
    -   - **Example**: `FIREFOX_102_8_0esr_BUILD1`
    47 
    -- [ ] Find the analogous `gecko-dev` commit: https://github.com/mozilla/gecko-dev
    48 
    -  - **Tip**: Search for unique string (like the Differential Revision ID) found in the mercurial commit in the `gecko-dev/esr102` branch to find the equivalent commit
    49 
    -  - **Example**: `3a3a96c9eedd02296d6652dd50314fccbc5c4845`
    50 
    -- [ ] Sign and Tag `gecko-dev` commit
    51 
    -  - Sign/Tag `gecko-dev` commit :
    52 
    -    - **Tag**: `$(ESR_TAG)`
    53 
    -    - **Message**: `Hg tag $(ESR_TAG)`
    45 
    +- [ ] Fetch Mozilla's firefox repo and identify this release's ${ESR_TAG}
    54 46 
     - [ ] Create new stable `base-browser` branch from tag
    55 47 
       - Branch name in the form: `base-browser-$(ESR_VERSION)esr-$(BROWSER_MAJOR).$(BROWSER_MINOR)-1`
    56 48 
       - **Example**: `base-browser-102.8.0esr-12.0-1`
    ... ... @@ -122,4 +114,4 @@
    122 114
    123 115 
     /label ~"Apps::Product::TorBrowser"
    124 116 
     /label ~"Apps::Type::Rebase"
    125 
    -/label ~"Apps::Priority::Blocker"
    117 
    +/label ~"Priority::Blocker"

  • .gitlab/issue_templates/062 Rebase - Legacy.md
    ... ... @@ -29,31 +29,19 @@
    29 29
    30 30 
     - [ ] In [Repository Settings](https://gitlab.torproject.org/tpo/applications/tor-browser/-/settings/repository):
    31 31 
       - [ ] Remove previous legacy `base-browser` and `tor-browser` branch protection rules (this will prevent pushing new changes to the branches being rebased)
    32 
    -  - [ ] Create new `base-browser` and `tor-browser` branch protection rule:
    33 
    -    - **Branch**: `*-$(ESR_VERSION)esr-13.5-1*`
    34 
    -      - **Example**: `*-115.18.0esr-13.5-1*`
    32 
    +  - [ ] Create new `tor-browser` branch protection rule:
    33 
    +    - **Branch**: `tor-browser-$(ESR_VERSION)esr-13.5-1*`
    34 
    +      - **Example**: `tor-browser-115.18.0esr-13.5-1*`
    35 35 
         - **Allowed to merge**: `Maintainers`
    36 36 
         - **Allowed to push and merge**: `Maintainers`
    37 37 
         - **Allowed to force push**: `false`
    38 38
    39 39 
     ### **Identify the Firefox Tagged Commit and Create New Branches**
    40 40
    41 
    -- [ ] Find the Firefox mercurial tag here: https://hg.mozilla.org/releases/mozilla-esr102/tags
    42 
    -   - **Example**: `FIREFOX_115_18_0esr_BUILD1`
    43 
    -- [ ] Find the analogous `gecko-dev` commit: https://github.com/mozilla/gecko-dev
    44 
    -  - **Tip**: Search for unique string (like the Differential Revision ID) found in the mercurial commit in the `gecko-dev/esr115` branch to find the equivalent commit
    45 
    -  - **Example**: `293d490d2e8d9fbb91c76336288f1287cbe285fb`
    46 
    -- [ ] Sign and Tag `gecko-dev` commit
    47 
    -  - Sign/Tag `gecko-dev` commit :
    48 
    -    - **Tag**: `$(ESR_TAG)`
    49 
    -    - **Message**: `Hg tag $(ESR_TAG)`
    50 
    -- [ ] Create new legacy `base-browser` branch from tag
    51 
    -  - Branch name in the form: `base-browser-$(ESR_VERSION)esr-13.5-1`
    52 
    -  - **Example**: `base-browser-115.18.0esr-13.5-1`
    41 
    +- [ ] Fetch Mozilla's firefox repo and identify this release's ESR-115 ${ESR_TAG}
    53 42 
     - [ ] Create new legacy `tor-browser` branch from
    54 43 
       - Branch name in the form: `tor-browser-$(ESR_VERSION)esr-13.5-1`
    55 44 
       - **Example**: `tor-browser-115.18.0esr-13.5-1`
    56 
    -- [ ] Push new `base-browser` branch to `upstream`
    57 45 
     - [ ] Push new `tor-browser` branch to `upstream`
    58 46 
     - [ ] Push new `$(ESR_TAG)` to `upstream`
    59 47
    ... ... @@ -61,22 +49,13 @@
    61 49
    62 50 
     - [ ] Checkout a new local branch for the `tor-browser` rebase
    63 51 
       - **Example**: `git branch tor-browser-rebase FIREFOX_115_18_0esr_BUILD1`
    64 
    -- [ ] **(Optional)** `base-browser` rebase
    65 
    -  - **NOTE** This step may be skipped if the `HEAD` of the previous `base-browser` branch is a `-buildN` tag
    66 
    -  - [ ] Cherry-pick the previous `base-browser` commits up to `base-browser`'s `buildN` tag onto new `base-browser` rebase branch
    67 
    -    - **Example**: `git cherry-pick FIREFOX_115_17_0esr_BUILD1..base-browser-115.17.0esr-13.5-1-build2`
    68 
    -  - [ ] Rebase and autosquash these cherry-picked commits
    69 
    -    - **Example**: `git rebase --autosquash --interactive FIREFOX_115_18_0esr_BUILD1 HEAD`
    70 
    -  - [ ] Cherry-pick remainder of patches after the `buildN` tag
    71 
    -    - **Example**: `git cherry-pick base-browser-115.17.0esr-13.5-1-build21..upstream/base-browser-115.17.0esr-13.5-1`
    72 52 
     - [ ] `tor-browser` rebase
    73 53 
       - [ ] Note the current git hash of `HEAD` for `tor-browser` rebase+autosquash step: `git rev-parse HEAD`
    74 
    -  - [ ] Cherry-pick the appropriate previous `tor-browser` branch's commit range up to the last `tor-browser` `buildN` tag
    75 
    -    - **Example**: `git cherry-pick base-browser-115.17.0esr-13.5-1-build1..tor-browser-115.17.0esr-13.5-1-build2
    76 
    -    - **Example (if separate base-browser rebase was skipped)**: `git cherry-pick FIREFOX_115_17_0esr_BUILD1..tor-browser-115.17.0esr-13.5-1-build2`
    54 
    +  - [ ] Cherry-pick the appropriate previous `tor-browser` branch's commit range up to the last `tor-browser` `build1` tag
    55 
    +    - **Example**: `git cherry-pick FIREFOX_115_17_0esr_BUILD1..tor-browser-115.17.0esr-13.5-1-build2`
    77 56 
       - [ ] Rebase and autosquash these newly cherry-picked commits: `git rebase --autosquash --interactive $(PREV_HEAD)`
    78 57 
          - **Example**: `git rebase --autosquash --interactive FIREFOX_115_18_0esr_BUILD1`
    79 
    -  - [ ] Cherry-pick remainder of patches after the last `tor-browser` `buildN` tag
    58 
    +  - [ ] Cherry-pick remainder of patches after the last `tor-browser` `build1` tag
    80 59 
         - **Example**: `git cherry-pick tor-browser-115.17.0esr-13.5-1-build1..upstream/tor-browser-115.17.0esr-13.5-1`
    81 60 
       - [ ] Rebase and autosquash again, this time replacing all `fixup` and `squash` commands with `pick`. The goal here is to have all of the `fixup` and `squash` commits beside the commit which they modify, but kept un-squashed for easy debugging/bisecting.
    82 61 
         - **Example**: `git rebase --autosquash --interactive FIREFOX_115_18_0esr_BUILD1`
    ... ... @@ -86,14 +65,11 @@
    86 65 
         - `git diff $(ESR_TAG_PREV)..$(BROWSER_BRANCH_PREV) > current_patchset.diff`
    87 66 
         - `git diff $(ESR_TAG)..$(BROWSER_BRANCH) > rebased_patchset.diff`
    88 67 
         - diff `current_patchset.diff` and `rebased_patchset.diff`
    89 
    -      - If everything went correctly, the only lines which should differ should be the lines starting with `index abc123...def456` (unless the previous `base-browser` branch includes changes not included in the previous `tor-browser` branch)
    68 
    +      - If everything went correctly, the only lines which should differ should be the lines starting with `index abc123...def456`
    90 69 
       - [ ] rangediff: `git range-diff $(ESR_TAG_PREV)..$(TOR_BROWSER_BRANCH_PREV) $(ESR_TAG)..HEAD`
    91 70 
         - **Example**: `git range-dif FIREFOX_115_17_0esr_BUILD1..upstream/tor-browser-115.17.0esr-13.5-1 FIREFOX_115_18_0esr_BUILD1..HEAD`
    92 71 
     - [ ] Open MR for the `tor-browser` rebase
    93 72 
     - [ ] Merge
    94 
    -- Update and push `base-browser` branch
    95 
    -  - [ ] Reset the new `base-browser` branch to the appropriate commit in this new `tor-browser` branch
    96 
    -  - [ ] Push these commits to `upstream`
    97 73
    98 74 
     ### **Sign and Tag**
    99 75
    ... ... @@ -104,13 +80,6 @@
    104 80 
         ./tools/browser/sign-tag.torbrowser legacy build1
    105 81 
         ```
    106 82 
       - [ ] Push tag to `upstream`
    107 
    -- [ ] Sign/Tag HEAD of the merged `base-browser` branch:
    108 
    -  - In **tor-browser.git**, checkout the new legacy `base-browser` branch
    109 
    -  - In **tor-browser-build.git**, run signing script:
    110 
    -    ```bash
    111 
    -    ./tools/browser/sign-tag.basebrowser legacy build1
    112 
    -    ```
    113 
    -  - [ ] Push tag to `upstream`
    114 83
    115 84 
     <!-- Do not edit beneath this line <3 -->
    116 85
    ... ... @@ -118,4 +87,4 @@
    118 87
    119 88 
     /label ~"Apps::Product::TorBrowser"
    120 89 
     /label ~"Apps::Type::Rebase"
    121 
    -/label ~"Apps::Priority::Blocker"
    90 
    +/label ~"Priority::Blocker"

  • .gitlab/issue_templates/063 Rebase - Rapid.md
    ... ... @@ -128,9 +128,9 @@ gitGraph:
    128 128
    129 129 
     - [ ] In [Repository Settings](https://gitlab.torproject.org/tpo/applications/tor-browser/-/settings/repository):
    130 130 
       - [ ] Remove previous nightly `tor-browser` branch protection rules (this will prevent pushing new changes to the branches being rebased)
    131 
    -  - [ ] Create new `tor-browser` branch protection rule:
    132 
    -    - **Branch**: `tor-browser-$(NIGHTLY_VERSION)-$(BROWSER_VERSION)-*`
    133 
    -      - **Example**: `tor-browser-130.0a1-15.0-*`
    131 
    +  - [ ] Create new `base-browser` and `tor-browser` branch protection rule:
    132 
    +    - **Branch**: `(tor|base)-browser-$(NIGHTLY_VERSION)-$(BROWSER_VERSION)-*`
    133 
    +      - **Example**: `(tor|base)-browser-130.0a1-15.0-*`
    134 134 
         - **Allowed to merge**: `Maintainers`
    135 135 
         - **Allowed to push and merge**: `Maintainers`
    136 136 
         - **Allowed to force push**: `false`
    ... ... @@ -138,15 +138,8 @@ gitGraph:
    138 138
    139 139 
     ### **Create New Branches**
    140 140
    141 
    -- [ ] Find the Firefox mercurial tag `$(NIGHTLY_TAG)`
    142 
    -  - Go to https://hg.mozilla.org/mozilla-central/tags
    143 
    -  - Find and inspect the commit tagged with `$(NIGHTLY_TAG)`
    144 
    -    - Tags are in yellow in the Mercurial web UI
    145 
    -  - Find the equivalent commit in https://github.com/mozilla/gecko-dev/commits/master
    146 
    -    - **Notice**: GitHub sorts commits by time, you might want to use `git log gecko-dev/master` locally, instead
    147 
    -    - Using the differential revision link is useful to quickly find the git commit
    148 
    -  - Sign/Tag the `gecko-dev` commit: `git tag -as $(NIGHTLY_TAG) $(GIT_HASH) -m "Hg tag $(NIGHTLY_TAG)"`
    149 
    -- [ ] Create two new rapid `tor-browser` branches from Firefox mercurial tag
    141 
    +- [ ] Fetch Mozilla's firefox repo and identify this release's ${NIGHTLY_TAG}
    142 
    +- [ ] Create two new rapid `tor-browser` branches from Firefox ${NIGHTLY_TAG}
    150 143 
       - Branch name in the form: `tor-browser-$(NIGHTLY_VERSION)-$(BROWSER_VERSION)-${BRANCH_NUM}`
    151 144 
       - **Example**: `tor-browser-130.0a1-15.0-1` and `tor-browser-130.0a1-15.0-2`
    152 145 
     - [ ] Push new `tor-browser` branches and the `firefox` tag to `upstream`
    ... ... @@ -297,4 +290,4 @@ gitGraph:
    297 290
    298 291 
     /label ~"Apps::Product::TorBrowser"
    299 292 
     /label ~"Apps::Type::Rebase"
    300 
    -/label ~"Apps::Priority::High"
    293 
    +/label ~"Priority::High"

  • .gitlab/issue_templates/080 Security Backports.md
    ... ... @@ -84,4 +84,4 @@
    84 84 
     /label ~"Apps::Product::TorBrowser"
    85 85 
     /label ~"Apps::Product::MullvadBrowser"
    86 86 
     /label ~"Apps::Type::Backport"
    87 
    -/label ~"Apps::Priority::Blocker"
    87 
    +/label ~"Priority::Blocker"

  • .gitlab/issue_templates/090 Emergency Security Issue.md
    ... ... @@ -101,5 +101,5 @@ Godspeed! :pray:
    101 101 
     /label ~"Apps::Product::TorBrowser"
    102 102 
     /label ~"Apps::Product::MullvadBrowser"
    103 103 
     /label ~"Apps::Type::Bug"
    104 
    -/label ~"Apps::Priority::Blocker"
    104 
    +/label ~"Priority::Blocker"
    105 105 
     /label ~"Emergency"

  • .gitlab/issue_templates/100 Release QA - Desktop.md
    ... ... @@ -209,4 +209,4 @@ Please lay claim to a platform in the comments:
    209 209
    210 210 
     /label ~"Apps::Product::TorBrowser"
    211 211 
     /label ~"Apps::Type::Test"
    212 
    -/label ~"Apps::Priority::Blocker"
    212 
    +/label ~"Priority::Blocker"

  • .gitlab/issue_templates/101 Release QA - Android.md
    ... ... @@ -104,4 +104,4 @@ Architectures:
    104 104
    105 105 
     /label ~"Apps::Product::TorBrowser"
    106 106 
     /label ~"Apps::Type::Test"
    107 
    -/label ~"Apps::Priority::Blocker"
    107 
    +/label ~"Priority::Blocker"

  • .gitlab/issue_templates/110 Bugzilla Triage.md → .gitlab/issue_templates/110 Firefox Release Review.md
    1 
    -# 📋 Bugzilla Triage
    1 
    +# 📋 Firefox Release Review
    2 2
    3 3 
     **NOTE** This issue presumes the branches and tags for the next Firefox release have already been created in tor-browser.git
    4 4
    5 
    +## Bugzilla Triage
    6 
    +
    5 7 
     - [ ] Generate Bugzilla triage CSV
    6 8 
       - Run (from `tor-browser-build` root):
    7 9 
       ```bash
    8 
    -    ./tools/browser/generate-bugzilla-triage-csv ${FIREFOX_VERSION} ${PREVIOUS_NIGHTLY_TAG} ${NEXT_NIGHLTY_TAG} ${TRIAGE_ISSUE_NUMBER} ${REVIEWERS} > out.csv
    10 
    +    ./tools/browser/generate-bugzilla-triage-csv ${FIREFOX_VERSION} ${PREVIOUS_NIGHTLY_TAG} ${NEXT_NIGHLTY_TAG} ${TRIAGE_ISSUE_NUMBER} > out.csv
    9 11 
       ```
    10 12 
       - `${FIREFOX_VERSION}`: the major Firefox version of the nightly to review
    11 13 
         - **Example**: 129
    ... ... @@ -15,42 +17,50 @@
    15 17 
         - **Example**: `FIREFOX_NIGHTLY_129_END`
    16 18 
       - `${TRIAGE_ISSUE_NUMBER}`: this `tor-browser` issue
    17 19 
         - **Example**: `43303`
    18 
    -  - `${REVIEWERS}`: `morgan` and two additional devs to triage this Firefox version
    19 
    -    - `boklm`
    20 
    -    - `brizental`
    21 
    -    - `clairehurst`
    22 
    -    - `dan`
    23 
    -    - `henry`
    24 
    -    - `jwilde`
    25 
    -    - `ma1`
    26 
    -    - `pierov`
    27 20 
       - **Example**:
    28 21 
         ```bash
    29 
    -    ./tools/browser/generate-bugzilla-triage-csv 129 FIREFOX_NIGHTLY_128_END FIREFOX_NIGHTLY_129_END 43303 morgan pierov henry > 129.csv
    22 
    +    ./tools/browser/generate-bugzilla-triage-csv 129 FIREFOX_NIGHTLY_128_END FIREFOX_NIGHTLY_129_END 43303 > 129.csv
    30 23 
         ```
    31 24 
     - [ ] Attach the generated CSV file to the triage isssue
    32 25 
     - [ ] Import to Google Sheets ( https://sheets.google.com )
    33 
    -  - [ ] Create blank spreadsheet
    34 
    -  - [ ] **Title**: `Bugzilla Triage ${VERSION}`
    35 
    -  - [ ] Import CSV: File > Import > Upload
    26 
    +  - Create blank spreadsheet
    27 
    +    - **Title**: `Bugzilla Triage ${VERSION}`
    28 
    +  - Import CSV: File > Import > Upload
    36 29 
         - **Import location**: "Replace spreadsheet"
    37 30 
         - **Separator type**: "Comma"
    38 31 
         - **Convert text to numbers, dates, and fomulas**: "✅"
    39 
    -  - [ ] Convert 'Review' column's issue cells to check-boxes:
    32 
    +  - Convert 'Review' column's issue cells to check-boxes:
    40 33 
         - Select relevant cells (i.e.: `A2:A1554` for in the 129 triage)
    41 34 
         - Insert > Checkbox
    42 
    -  - [ ] Convert 'Triaged by' cells to check-boxes
    43 
    -  - [ ] Share Spreadsheet
    35 
    +  - Convert 'Triaged by' cells to check-boxes
    36 
    +  - Share Spreadsheet
    44 37 
         - 🔒 Share > General access
    45 38 
           - Change `Restricted` to `Anyone with the link`
    46 39 
         - Post link in an internal note on this issue
    47 
    -- [ ] Page requested reviewers to this issue
    48 
    -- [ ] Triage Completed by:
    49 
    -  - [ ] morgan
    40 
    +- [ ] Assign requested reviewers to this issue
    41 
    +
    42 
    +## Release Notes Review
    43 
    +
    44 
    +<!--
    45 
    +  Ticket author! Find and post links to the release notes here!
    46 
    +    - Release notes for users: https://www.mozilla.org/en-US/firefox/releases/
    47 
    +    - Release notes for developers: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases
    48 
    +-->
    49 
    +
    50 
    +- [ ] Release Notes for Users (often includes multiple point releases):
    51 
    +  - https://www.mozilla.org/en-US/firefox/${FIREFOX_VERSION}/releasenotes/
    52 
    +- [ ] Release Notes for Developers
    53 
    +  - https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/${FIREFOX_VERSION}
    54 
    +
    55 
    +---
    56 
    +
    57 
    +- Bugzilla Triage and Release Notes Review Completed by:
    58 
    +  <!-- try and distribute the review responsibilities somehow fairly across the team -->
    50 59 
       - [ ] reviewer 1 <!-- replace with reviewer name :) -->
    51 60 
       - [ ] reviewer 2 <!-- replace with reviewer name :) -->
    61 
    +  - [ ] reviewer 3 <!-- replace with reviewer name :) -->
    52 62
    53 
    -/label ~"esr-140"
    54 63 
     /label ~"Apps::Product::TorBrowser"
    55 
    -/label ~"Apps::Type::Audit"
    56 
    -/label ~"Apps::Priority::Blocker"
    64 
    +/label ~"Apps::Type::Triage"
    65 
    +/label ~"Priority::Blocker"
    66 
    +/milestone %"Tor Browser 16.0"

  • .gitlab/issue_templates/120 Bugzilla Audit.md
    ... ... @@ -18,4 +18,4 @@ Title:
    18 18 
     /label ~"esr-140"
    19 19 
     /label ~"Apps::Product::TorBrowser"
    20 20 
     /label ~"Apps::Type::Audit"
    21 
    -/label ~"Apps::Priority::Blocker"
    21 
    +/label ~"Priority::Blocker"

  • .gitlab/issue_templates/Default.md
    ... ... @@ -23,5 +23,5 @@ Please select the appropriate issue template from the **Description** drop-down.
    23 23 
     - 🚨 **Emergency Security Issue** - manage fixing and publishing a critical security fix
    24 24 
     - ✅ **Release QA - Desktop** - test and verify functionality of our Desktop release
    25 25 
     - ✅ **Release QA - Android** - test and verify functionality of our Android release
    26 
    -- 📋 **Bugzilla Triage** - identify upstream Firefox issues which need to be audited
    26 
    +- 📋 **Firefox Release Review** - identify upstream Firefox issues which need to be audited
    27 27 
     - 🔍 **Bugzilla Audit** - determine if/how an upstream change affects the browser

    • —
    View it on GitLab.
    You're receiving this email because of your account on gitlab.torproject.org. Manage all notifications · Help Notification message regarding https://gitlab.torproject.org/tpo/applications/tor-browser/-/compare/2e5205280915b9f5b6fb86e92ef1543b002e92e8...283e83c98dd1d6cd4270cea7736ae86219fc9086 at 1755184307