|
|
|
# Releases
|
|
|
|
|
|
|
|
Network team is responsible for Core Tor releases, we aim to have a new release
|
|
|
|
Network team is responsible for Core Tor releases. We aim to have a new release
|
|
|
|
every 6 months.
|
|
|
|
|
|
|
|
Please check our [Release Guidelines](./ReleaseGuidelines) for more
|
|
|
|
detailed information on the process.
|
|
|
|
detailed information on the process. (This hasn't been updated for a while.)
|
|
|
|
|
|
|
|
Please check our [Release Parameters](./ReleaseParameters) for more
|
|
|
|
detailed information on what protocol version or consensus parameters will
|
|
|
|
affect the network.
|
|
|
|
affect the network. (This hasn't been updated for a while, and we should use it more.)
|
|
|
|
|
|
|
|
## Support policy
|
|
|
|
## Support policies
|
|
|
|
|
|
|
|
Releases can either be "regular" or "long-term support" ("LTS"). Regular
|
|
|
|
releases are supported for 9 months after they become stable or for 3 months
|
|
|
|
after the next release becomes stable -- whichever is longer. LTS releases are
|
|
|
|
supported for some time announced in advance -- typically, 3 years.
|
|
|
|
|
|
|
|
For all supported releases, we intend that:
|
|
|
|
|
|
|
|
* Information needed to connect to the Tor network (directory authorities, fallback directories, geoip tables) will be kept up-to-date.
|
|
|
|
* Important security issues will get fixed.
|
|
|
|
* Major stability issues will get fixed.
|
|
|
|
* Portability regressions will get fixed.
|
|
|
|
* Portability bugs to major supported platforms will get fixed.
|
|
|
|
|
|
|
|
For the most recent supported stable release only, we intend that:
|
|
|
|
|
|
|
|
* Misleading documentation will get fixed.
|
|
|
|
* Smaller bugs that significantly impact user experience will get fixed.
|
|
|
|
|
|
|
|
We do NOT expect:
|
|
|
|
|
|
|
|
* That unsupported releases will all work on the Tor network.
|
|
|
|
* That unsupported releases will all fail to work on the Tor network.
|
|
|
|
* That older supported releases will provide the same privacy as the newer ones.
|
|
|
|
|
|
|
|
Some features and configurations are currently only maintained in the two most
|
|
|
|
recent stable releases, either because they are less mature than the rest of
|
|
|
|
Tor, because there are relatively few users who need them, or for some other
|
|
|
|
reason:
|
|
|
|
|
|
|
|
* Running a directory authority.
|
|
|
|
* Enabling Rust support.
|
|
|
|
* Enabling NSS support.
|
|
|
|
* Embedding Tor in another binary.
|
|
|
|
* Getting volunteer-submitted patches to run on [unsupported platforms (Tier 3 or lower)](./SupportedPlatforms).
|
|
|
|
|
|
|
|
The above policy is our intent, but not a promise. We'll make a solid effort to follow it.
|
|
|
|
Please see our [Support Policy](./SupportPolicy) for information on how long we support each release series, and which kinds of patches are eligible for backport.
|
|
|
|
|
|
|
|
## Calendar:
|
|
|
|
_Best effort dates. May change over time. (When they do, we generally use ~~Strikethrough~~ to indicate the change.)_
|
| ... | ... | |
