... | ... | @@ -4,7 +4,7 @@ |
|
|
Network Team. We try to follow very tightly the following policy but keep in
|
|
|
mind that special cases can arise.
|
|
|
|
|
|
**Adopted On**: ...
|
|
|
**Adopted On**: May 9th, 2022
|
|
|
|
|
|
## Types of Releases
|
|
|
|
... | ... | @@ -35,8 +35,9 @@ 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.
|
|
|
|
|
|
See our deprecation of C tor [page](./NetworkTeam/DeprecationTor.md) for more
|
|
|
details on what can be safely contributed to tor.git.
|
|
|
See our deprecating C tor patches policy
|
|
|
[page](./NetworkTeam/DeprecatingCPatches.md) for more details on what can be
|
|
|
safely contributed to tor.git.
|
|
|
|
|
|
## Levels of Support
|
|
|
|
... | ... | @@ -78,7 +79,7 @@ are where most bugs will be encountered. |
|
|
|
|
|
## Unstable Features
|
|
|
|
|
|
Above we describe circumstances when a release is "supported". Even in
|
|
|
Above we describe circumstances when a release is "supported". Even in
|
|
|
supported releases, however, some unstable features may not receive fixes,
|
|
|
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.
|
... | ... | |