tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

status-flags.rst (1835B)


      1 Release Status Flags
      2 ====================
      3 
      4 The flag ``status_firefoxN`` has many values, here’s a cheat sheet.
      5 
      6 +---------+------------+------------+--------------+-------------------+
      7 | \-\-\-  | \?         | unaffected | affected     | fixed             |
      8 +=========+============+============+==============+===================+
      9 | \?      | unaffected |            | wontfix      | verified          |
     10 +---------+------------+------------+--------------+-------------------+
     11 |         | affected   |            | fix-optional | disabled          |
     12 +---------+------------+------------+--------------+-------------------+
     13 |         |            |            | fixed        | verified disabled |
     14 +---------+------------+------------+--------------+-------------------+
     15 
     16 The headers of the table are values of the status flag. Each column are
     17 the states reachable from the column headings.
     18 
     19 -  ``---`` we don’t know whether Firefox N is affected
     20 -  ``?`` we don’t know whether Firefox N is affected, but we want to find
     21   out
     22 -  ``affected`` - present in this release
     23 -  ``unaffected`` - not present in this release
     24 -  ``fixed`` - a contributor has landed a change set in the tree
     25   to address the issue
     26 -  ``verified`` - the fix has been verified by QA or other contributors
     27 -  ``disabled`` - the fix or the feature has been backed out or disabled
     28 -  ``verified disabled`` - QA or other contributors confirmed the fix or
     29   the feature has been backed out or disabled
     30 -  ``wontfix`` - we have decided not to accept/uplift a fix for this
     31   release cycle (it is not the same as the bug resolution WONTFIX).
     32   This can also mean that we don’t know how to fix that and will ship
     33   with this bug
     34 -  ``fix-optional`` - we would take a fix for the current release but
     35   don’t consider it as important/blocking for the release