#28462: tor 0.3.6 + 0.4.0 missing in "relays by version" graph -----------------------------+------------------------------ Reporter: nusenu | Owner: metrics-team Type: defect | Status: new Priority: Medium | Milestone: Component: Metrics/Website | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------+------------------------------
Comment (by karsten): In fact, this ''is'' now automated: as soon as a major version (like 0.3.6 or 0.4.0) is first recommended by the directory authorities, it is added to the graph, including past days/weeks/months when the major version was not yet recommended. The reason for requiring the recommendation bit is that nobody should be able to add a hundred new versions to the graph just for fun. And the reason for automating it at all is to not require new tickets for new versions. Does this make sense? Is there a better way for automating it? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28462#comment:1> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs