...

Changes in version 0.2.9.10 - 2017-03-01 [...]

Starting this new version results in the following log entry:

This version of Tor (0.2.9.10) is newer than any recommended version in its series, according to the directory authorities. Recommended versions are: 0.2.4.27,0.2.4.28,0.2.5.12,0.2.5.13,0.2.7.6,0.2.7.7,0.2.8.9,0.2.8.10,0.2.8.11,0.2.8.12,0.2.9.9,0.3.0.2-alpha,0.3.0.3-alpha

Not sure if this is just informational or if it will affect Tor node operation.

This is just sub-optimal timing. Ideally tor dir auths would add new versions before they get released to the recommended versions list but in this case only moria1 was in time [1]. This log message should no longer appear as soon as tor26 or gabelmoo adds the new releases [2].

Maybe it would make sense to add support for version ranges so not every new release would require two dir auth operators to touch their configuration.

[1] https://lists.torproject.org/pipermail/tor-consensus-health/2017-March/00774... [2] https://consensus-health.torproject.org/#recommendedversions