... | ... | @@ -17,9 +17,9 @@ A Tor (tor.git) release can be in one of 4 states: |
|
|
|
|
|
Once a release becomes `stable`, any previous stable release becomes
|
|
|
`oldstable`. The release will remain `oldstable` for **3 months** or until Tor
|
|
|
Browser transitions out of it. The 3 months is to give time for packagers to
|
|
|
package and roll out the new stable. We also provide this timeline for the
|
|
|
network relay operators to migrate to the new stable.
|
|
|
Browser transitions out of it. This grace period is to give time for packagers
|
|
|
to roll out the new stable. We also provide this period for the network relay
|
|
|
operators to migrate to the new stable.
|
|
|
|
|
|
After that, the release will be considered `End of Life (EOL)` as in
|
|
|
unsupported meaning that at any point after that state is set for the release
|
... | ... | @@ -31,21 +31,18 @@ At the moment, we are actively working on |
|
|
[arti](https://gitlab.torproject.org/tpo/core/arti/) as a
|
|
|
[tor.git](https://gitlab.torproject.org/tpo/core/tor/) replacement.
|
|
|
|
|
|
In late 2022, `arti` will replace `tor.git` as the defacto **client** to be
|
|
|
used which makes us currently restricting **client features** going in
|
|
|
`tor.git` to only the funded project.
|
|
|
In late 2022 or start of 2023, `arti` will replace `tor.git` as the defacto
|
|
|
**client** to be used which makes us currently restricting **client features**
|
|
|
going in `tor.git` to only the funded project.
|
|
|
|
|
|
We **strongly** encourage contributors to develop client side features in
|
|
|
`arti` from now on as there are little changes that we'll accept them in
|
|
|
`tor.git`.
|
|
|
|
|
|
All relays side features are still planned for `tor.git` at the moment.
|
|
|
See our deprecation of C tor [page](./NetworkTeam/DeprecationTor.md) for more
|
|
|
details on what can be safely contributed to tor.git.
|
|
|
|
|
|
## Levels of Support
|
|
|
|
|
|
Note that we update **data** that is required or recommended for connecting to
|
|
|
the Tor network, including authority lists, fallback directory lists, and
|
|
|
geoip configuration in all supported releases.
|
|
|
Note that, in all supported releases, we update **data** that is required or
|
|
|
recommended for connecting to the Tor network, including authority lists,
|
|
|
fallback directory lists, and geoip configuration.
|
|
|
|
|
|
In **alpha** release series:
|
|
|
|
... | ... | |