Labels

Issue for tracking other multi-part issues (e.g. major features, infrastructure changes, etc)

Issue for some how improving the user experience without fundamentally changing functionality (e.g. updating icons, improving aria labelling, tweaking layout padding, etc)

Issue for a proposed feature (e.g. set circuit exit node country, allow users to spoof geolocation, etc)

Issue for rebasing Tor Browser (e.g. minor ESR, rapid-release, etc)

Issue for tracking a browser release (e.g. Prepare Tor Browser Alpha 14.5a3)

Issue for anything test-related (e.g. developing mochi tests, building test infrastructure, manual QA, etc)

Issue for triaging or filtering a big list of things (e.g. upstream Rapid Release issue triage for further auditing)

Issue for uplifting a changeset to upstream projects (e.g. Firefox, MinGW, etc)

Issue for reporting website breakage due to our browser customisations (e.g. foo.com's images are corrupted and unusable, bar.com serves endless CAPTCHAs,e tc)

Build/Test/Development automation related issues

Any tickets that needs to be backported

Issues that are blocked by other work/issue. Please add a comment to the issue when marking it with this label.

An issue requiring work on brand and/or visual assets, e.g. illustration, iconography, brand design et cetera.

Any issue (outside the Applications group) that need work from the Applications team.

A possible bug and how to reproduce it

All tickets which work can be supported through the Bug Smash Fund Campaign.

Issues related to the build system

Continuous Integration