Latest upstream release: 0.2.0.35 Current version in rawhide-source: 0.2.0.34 URL: http://tor.eff.org/dist/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Using_FEver_to_track_upstream_changes
Rawhide build 0.2.0.35 failed: http://koji.fedoraproject.org/koji/buildinfo?buildID=111851 Scratch build nowadays fails due to LaTeX documentation generation problem: http://koji.fedoraproject.org/koji/taskinfo?taskID=1484311
Latest upstream release: 0.2.1.18 Current version in Fedora Rawhide: 0.2.0.34 URL: http://tor.eff.org/dist/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Using_FEver_to_track_upstream_changes
Mmm. This is wrong. 0.2.1.xx is unstable branch. FEver list might need some bump to ignore 0.2.1.xx till it's stable.
(In reply to comment #3) > Mmm. This is wrong. 0.2.1.xx is unstable branch. FEver list might need some > bump to ignore 0.2.1.xx till it's stable. Will the 0.2.1.xx branch be declared stable or will the next stable branch be 0.2.2.xx? Maybe this regex could be used: tor-([0-9]\.[0-9]\.[0,2,4,6,8]\.[0-9]*).tar.gz
Actually, I've been in contact with upstream and it turns out that 0.2.1.x is now the stable branch since the release of 0.2.1.19. This means that only bugfixes will go into 0.2.1.x from now on and new development will happen in a new 0.2.2.x branch. This can be deduced from the download page https://www.torproject.org/download-unix.html.en where the new stable is now updated. There are a lot of useful stuff in this new release, and my understanding is that the 0.2.0.x branch is now no longer supported from upstream. There is no statement with regards to configuration compatibility that I have found on this new major release from upstream, but some casual testing indicates that there are no incompatible changes to the config file syntax.
Indeed. I wish they stated that 0.2.1.xx is stable more explicitly, though.
should be now in rawhide; I will see whether/when I backport it to F11 or F10
Excellent. I think that backporting the new stable tor to current Fedora releases would be a good idea. I have anecdotal evidence that existing configuration files work without modification, and I am currently conducting some email conversations with the tor maintenance team that I hope will lead to some official statement with regards to the status of the 0.2.0.x branch.