#32672: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()
-------------------------------------------------+-------------------------
Reporter: teor | Owner: neel
Type: task | Status:
| merge_ready
Priority: Medium | Milestone: Tor:
| 0.4.4.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: 044-should, 043-backport, | Actual Points:
041-backport, 042-backport, consider- |
backport-after-authority-test, fast-fix, |
network-health |
Parent ID: | Points: 0.5
Reviewer: teor | Sponsor:
-------------------------------------------------+-------------------------
Comment (by teor):
The last release of 0.2.9 was 13 months ago. Even before then, we didn't
backport all our fixes to 0.2.9. And there have been no new features in
0.2.9 for 3-4 years.
0.4.0's last release was a month or two ago, it's reasonably up-to-date.
If we patch any security issues, we won't patch 0.2.9 or 0.4.0. If we
decide that security fix is required, we might need to reject them
straight after the release of the fix. We don't really control the timing
of security fixes.
This is a directory authority fix. We don't support directory authorities
older than the last two stable releases. That's 0.4.1 right now, and it
will be 0.4.2 by the time 0.4.4 is in feature freeze.
Feature freeze for 0.4.2 is May 15 2020:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases#Current
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32672#comment:27>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
