morgan pushed to branch main at The Tor Project / Applications / tor-browser-build

Commits:

11 changed files:

Changes:

  • .gitlab/issue_templates/000 Bug Report.md
    1 
    +# 🐞 Bug Report
    2 
    +<!--
    3 
    +Use this template to report problems with the build system. Runtime
    4 
    +bugs for products built by the build system should be opened in their
    5 
    +respective repositories:
    6 
    +- Tor Browser: https://gitlab.torproject.org/tpo/applications/tor-browser
    7 
    +- Mullvad Browser: https://gitlab.torproject.org/tpo/applications/mullvad-browser
    8 
    +- Tor VPN: https://gitlab.torproject.org/tpo/applications/vpn/
    9 
    +
    10 
    +The issue's title MUST provide a succinct description of the problem.
    11 
    +
    12 
    +Some good (hypothetical) titles:
    13 
    +- Required perl dependency missing from debian repositories
    14 
    +- Tor Browser macOS builds not reproducible
    15 
    +- Intermittent failure running make fetch
    16 
    +
    17 
    +Please DO NOT include information about platform in the title, it is redundant
    18 
    +with our labeling system!
    19 
    +-->
    20 
    +
    21 
    +## Reproduction steps
    22 
    +<!--
    23 
    +Provide specific steps developers can follow to reproduce your issue.
    24 
    +-->
    25 
    +
    26 
    +## Expected behaviour
    27 
    +<!--
    28 
    +Provide a description of the expected results.
    29 
    +-->
    30 
    +
    31 
    +## Actual behaviour
    32 
    +<!--
    33 
    +Provide a description of what actually occurs and any relevant logs.
    34 
    +-->
    35 
    +
    36 
    +## Host Environment
    37 
    +<!--
    38 
    +Please provide information about your host build environment (Linux distribution, version,
    39 
    +CPU architecture, etc)
    40 
    +-->
    41 
    +
    42 
    +/label ~"Apps::Product::BuildSystem"
    43 
    +/label ~"Apps::Type::Bug"

  • .gitlab/issue_templates/Backport.md → .gitlab/issue_templates/010 Backport.md
    1 
    +# ⬅️ Backport Patchset
    2 
    +
    1 3 
     <!--
    2 4 
     Title:
    3 5 
         Backport tor-browser-build-browser#12345: Title of Issue
    ... ... @@ -5,24 +7,22 @@ Title:
    5 7 
     This is an issue for tracking back-porting a patch-set (e.g. from main to maint-15.0)
    6 8 
     -->
    7 9
    8 
    -## Backport Patchset
    9 
    -
    10 
    -### Book-keeping
    10 
    +## Book-keeping
    11 11
    12 
    -#### Gitlab Issue(s)
    12 
    +### Gitlab Issue(s)
    13 13 
     - tor-browser#12345
    14 14 
     - mullvad-browser#123
    15 15 
     - tor-browser-build#12345
    16 16
    17 
    -#### Merge Request(s)
    17 
    +### Merge Request(s)
    18 18 
     - tor-browser-build!1234
    19 19
    20 
    -#### Target Channels
    20 
    +### Target Channels
    21 21
    22 22 
     - [ ] maint-15.0
    23 23 
     - [ ] maint-13.5
    24 24
    25 
    -### Notes
    25 
    +## Notes
    26 26
    27 27 
     <!-- whatever additional info, context, etc that would be helpful for backporting -->
    28 28

  • .gitlab/issue_templates/020 Revert.md
    1 
    +# ❌ Revert Patchset
    2 
    +<!--
    3 
    +This is an issue for tracking reverting a patch-set (e.g. Time-gated features
    4 
    +which are no longer needed after the expiration date)
    5 
    +
    6 
    +Please ensure the title has the following format:
    7 
    +
    8 
    +- Revert tor-browser-build#12345: Title of original issue
    9 
    +-->
    10 
    +
    11 
    +## Bookkeeping
    12 
    +
    13 
    +### Time Window
    14 
    +<!--
    15 
    +When should this patchset be reverted?
    16 
    +-->
    17 
    +
    18 
    +- **Revert-After Date**
    19 
    +  - Date:
    20 
    +
    21 
    +### Issue(s)
    22 
    +<!-- issue associated with the original patchset -->
    23 
    +- tor-browser#xxxxx
    24 
    +- mullvad-browser#xyz
    25 
    +- tor-browser-build#xxxxx
    26 
    +
    27 
    +### Merge Request(s)
    28 
    +<!-- merge-request associated with the original patchset -->
    29 
    +- tor-browser-build!xxxx
    30 
    +
    31 
    +### Target Channels
    32 
    +<!-- Which channel has the commits we need to revert? -->
    33 
    +- [ ] main
    34 
    +- [ ] maint-15.0
    35 
    +
    36 
    +## Notes
    37 
    +
    38 
    +<!-- whatever additional info, context, etc that would be helpful for reverting -->
    39 
    +
    40 
    +
    41 
    +<!-- Do not edit beneath this line <3 -->
    42 
    +
    43 
    +---
    44 
    +
    45 
    +/label ~"Apps::Product::TorBrowserBuild"
    46 
    +/label ~"Apps::Type::Chore"

  • .gitlab/issue_templates/Uplift.md → .gitlab/issue_templates/030 Uplift.md
    1 
    +# ⬆️ Uplift Patchset
    2 
    +
    1 3 
     <!--
    2 4 
     Title:
    3 5 
         Uplift tor-browser-build#12345: Title of Issue
    ... ... @@ -6,20 +8,18 @@ This is an issue for tracking uplift of a patch-set to an upstream build-depende
    6 8
    7 9 
     -->
    8 10
    9 
    -## Uplift Patchset
    10 
    -
    11 
    -### Book-keeping
    11 
    +## Book-keeping
    12 12
    13 
    -#### Gitlab Issue(s)
    13 
    +### Gitlab Issue(s)
    14 14 
     - tor-browser-build#12345
    15 15
    16 
    -#### Merge Request(s)
    16 
    +### Merge Request(s)
    17 17 
     - tor-browser-build!1234
    18 18
    19 
    -#### Upstream Project Issue(s):
    19 
    +### Upstream Project Issue(s):
    20 20
    21 21
    22 
    -### Notes
    22 
    +## Notes
    23 23
    24 24 
     <!-- whatever additional info, context, etc that would be helpful for uplifting -->
    25 25

  • .gitlab/issue_templates/Release Prep - Tor Browser Alpha.md → .gitlab/issue_templates/040 Release Prep - Tor Browser Alpha.md
    1 
    -# Release Prep Tor Browser Alpha
    1 
    +# 🧅 Release Prep Tor Browser Alpha
    2 2
    3 3 
     - **NOTE** It is assumed the `tor-browser` alpha rebase and security backport tasks have been completed
    4 4 
     - **NOTE** This can/is often done in conjunction with the equivalent Mullvad Browser release prep issue

  • .gitlab/issue_templates/Release Prep - Tor Browser Stable.md → .gitlab/issue_templates/041 Release Prep - Tor Browser Stable.md
    1 
    -# Release Prep Tor Browser Stable
    1 
    +# 🧅 Release Prep Tor Browser Stable
    2 2
    3 3 
     - **NOTE** It is assumed the `tor-browser` release rebase and security backport tasks have been completed
    4 4 
     - **NOTE** This can/is often done in conjunction with the equivalent Mullvad Browser release prep issue

  • .gitlab/issue_templates/Release Prep - Tor Browser Legacy.md → .gitlab/issue_templates/042 Release Prep - Tor Browser Legacy.md
    1 
    -# Release Prep Tor Browser Legacy
    1 
    +# 🧅 Release Prep Tor Browser Legacy
    2 2
    3 3 
     - **NOTE** It is assumed the `tor-browser` release rebase and security backport tasks have been completed
    4 4

  • .gitlab/issue_templates/Release Prep - Mullvad Browser Alpha.md → .gitlab/issue_templates/050 Release Prep - Mullvad Browser Alpha.md
    1 
    -# Release Prep Mullvad Browser Alpha
    1 
    +# 🌐 Release Prep Mullvad Browser Alpha
    2 2
    3 3 
     - **NOTE** It is assumed the `mullvad-browser` alpha rebase and security backport tasks have been completed
    4 4 
     - **NOTE** This can/is often done in conjunction with the equivalent Tor Browser release prep issue

  • .gitlab/issue_templates/Release Prep - Mullvad Browser Stable.md → .gitlab/issue_templates/051 Release Prep - Mullvad Browser Stable.md
    1 
    -# Release Prep Mullvad Browser Stable
    1 
    +# 🌐 Release Prep Mullvad Browser Stable
    2 2
    3 3 
     - **NOTE** It is assumed the `mullvad-browser` release rebase and security backport tasks have been completed
    4 4 
     - **NOTE** This can/is often done in conjunction with the equivalent Tor Browser release prep issue

  • .gitlab/issue_templates/Release Prep - Tor VPN.md → .gitlab/issue_templates/060 Release Prep - Tor VPN.md
    1 
    -# Release Prep Tor VPN
    1 
    +# 🔑 Release Prep Tor VPN
    2 2
    3 3 
     - **NOTE** It is assumed the `vpn` release has been tagged in the `vpn.git` repository
    4 4

  • .gitlab/issue_templates/Default.md
    1 
    +# Open a new Issue
    2 
    +
    3 
    +Please select the appropriate issue template from the **Description** drop-down.
    4 
    +
    5 
    +---
    6 
    +
    7 
    +- 🐞 **Bug Report** - report a problem with the browser
    8 
    +- 💡 **Proposal** - suggest a new feature
    9 
    +
    10 
    +*NOTE*: the following issue types are intended for internal use
    11 
    +
    12 
    +- ⬅️ **Backport** - cherry-pick change to other release channels
    13 
    +- ❌ **Revert** - revert a change
    14 
    +- ⬆️ **Uplift** - uplift change to upstream project
    15 
    +- 🧅 **Release Prep - Tor Browser Alpha** - prepare a new Tor Browser Alpha Release
    16 
    +- 🧅 **Release Prep - Tor Browser Stable** - prepare a new Tor Browser Stable Release
    17 
    +- 🧅 **Release Prep - Tor Browser Legacy** - prepare a new Tor Browser Legacy Release
    18 
    +- 🌐 **Release Prep - Mullvad Browser Alpha** - prepare a new Mullvad Browser Alpha Release
    19 
    +- 🌐 **Release Prep - Mullvad Browser Stable** - prepare a new Mullvad Browser Stable Release
    20 
    +- 🔑 **Release Prep - Tor VPN** - prepare a new TorVPN Release

    • —
    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-build/-/compare/e75179ba9f5a0603a882da9084dce6763b468836...2ad598cb306a9be8be588ed7f0d0fe4247ab1143 at 1769512583