Release Policy

Previously, we used to follow a strict 6 months release schedule but we do not anymore because the majority of our engineering resources have now shifted to arti and thus we are now releasing tor.git on a "when we can and it is ready" basis.

Current Process

Alpha To Stable

Depending on active development and our roadmap, we try to regurlarly do alpha releases every few weeks over usually several months.

Once we are satisfied with an alpha, we then transition into a release candidate (rc) for which no more features are merged. That process usually takes couple weeks at most depending on the stability.

Finally, we release a stable when we believe it has been tested enough. Once the stable is released, we open the merge window for the next release series.

Old Stable

Once a stable series becomes old stable, that is a new stable was released, there are little very little chances that we'll do another oldstable release for that series.

We will in case we merge fixes as described by our support policy.

End of Life

Once a release series reach that state, nothing is done on it even in case of critical security issues.

Furthermore, directory authorities will reject EOL versions from the consensus.