Macintosh-SW/tenfourfox
1
0
Fork 0
mirror of https://github.com/classilla/tenfourfox.git synced 2024-06-09 11:29:39 +00:00
Code Issues Projects Releases Wiki Activity

update for security parity

Cameron Kaiser 2021-03-29 09:56:15 -07:00
parent d72aed82d2
commit 7c3bf3a454
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Parity.md

@ -10,10 +10,14 @@ After almost seven years, TenFourFox exited source parity with the end of suppor
**Feature parity**
This is the current state of TenFourFox. This parity level indicates that we are no longer building directly from a Mozilla repository but instead from our own codebase, which was once a Mozilla-supported repo and is no longer. Dropping to feature parity implies that the most current Mozilla as written cannot be hacked to compile anymore, so since our source is now necessarily diverging, we maintain it in our own repository ourselves.
This parity level indicated that we were no longer building directly from a Mozilla repository but instead from our own codebase, which was once a Mozilla-supported repo and is no longer. Dropping to feature parity implies that the most current Mozilla as written cannot be hacked to compile anymore, so since our source is now necessarily diverging, we maintain it in our own repository ourselves.
Feature parity implies that we will do our best, within technical limits, to match the feature set of the current Firefox even if we are not using the same source necessarily. This typically involves monitoring Mercurial changesets and Bugzilla bugs for patches, and adapting and/or applying them if they are deemed useful. Only useful or critical features will be so ported, to avoid turning the browser into a series of potentially unstable patches of patches. Security parity, naturally, is considered just this sort of critical patch, but other improvements to rendering and performance will also be considered. Also, feature parity does not preclude implementing our own custom features, since the code base is ours, which is a small advantage.
After over ten years, TenFourFox exited feature parity with Feature Parity Release 32 in April 2021.
**Security parity**
This means the browser has reached a point of maximum technical evolution, either due to completely incompatible code or the processing limits of aging machines, and is the terminal stage of support. Although some custom features may be added, the browser core is essentially in a state of arrested development. However, non-security bugs will still be fixed to the extent possible, and Mozilla security advisories will still be backported such that the browser will still be safe for day-to-day use even if it is no longer evolving technologically. Security parity state will likely persist for several years after source parity has ended.
This is the current state of TenFourFox. This means the browser has reached a point of maximum technical evolution, either due to completely incompatible code or the processing limits of aging machines, and is the terminal stage of support. Although some custom features may be added, the browser core is essentially in a state of arrested development. However, non-security bugs will still be fixed to the extent possible, and Mozilla security advisories will still be backported such that the browser will still be safe for day-to-day use even if it is no longer evolving technologically.
After September 7, 2021, no user builds will be made. While updates will occur to the Github tree, users are responsible for building their own local copies, and updates will not occur on any particular schedule with no guarantees of timeliness or function.