Comment 2 for bug 328442
Revision history for this message
| Martin Pitt (pitti) wrote Re: Tor 0.1.2.x abandoned by upstream | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
I still remember the thread, and back then we concluded that we can pursue the path of updating stables to new upstream versions if we get enough testing *and* the upgrade does not break existing user configuration. I subscribed motu-sru for their feedback as well, since the package is in universe.
Are there any configuration settings in 0.1.x. which are not handled any more by 0.2? If so, what happens for those?
Should we put the current intrepid package (2.0.31) into hardy-proposed? In other words, is 2.0.31 "good enough" for now? This would be slightly safer, since the intrepid version already got testing. We could then update all stable releases to a newer 0.2.x later, in a separate SRU.
Or rather update jaunty and intrepid-proposed to the latest upstream microrelease first (which should become a separate SRU bug, see above), test it, get it into intrepid-updates, and then backport this to hardy?
Thanks for any insight, Roger!