New release?

[ffontaine]

Latest release was made more than 2 years ago. It would be great to tag a new one that we could used for example in buildroot.

[rakshasa]

Just spent a month on rbedit, now that it is done I can continue with CI tests for ipv6. After that is done I'll make a release.

[ffontaine]

Thanks for your answer, this is great :+1:

[Drowze]

I'm excited to get this change released: https://github.com/rakshasa/rtorrent/commit/14d7121185a9efb66949e11a476e78e6933e857b

Just stumbled today on this issue: https://github.com/rakshasa/rtorrent/issues/874

[afontenot]

@rakshasa before any new release it would be worthwhile to have a look through and cherry pick features from a popular fork: https://github.com/jesec/rtorrent and https://github.com/jesec/libtorrent

In particular, someone has already submitted one PR fixing some memory leaks: https://github.com/rakshasa/rtorrent/pull/1095

I would be happy to extract clean patches that

• add support for initial seeding (changes also required to libtorrent)
• add support for sequential downloading (changes also required to libtorrent)

But there's some other work in there too that deserves a look, e.g. removing deprecated code, and a JSON-RPC API that looks quite nice. The latter might need some work to allow dynamic linking with the distribution provided nlohmann-json, I haven't tried it.

Maybe @jesec would even be kind enough to suggest stuff to upstream and submit PRs?

[Neustradamus]

@rakshasa: Have you progressed on this new release?

Please look all PRs, all forks, all issues:

• https://github.com/rakshasa/rtorrent/network
• https://github.com/rakshasa/rtorrent/pulls
• https://github.com/rakshasa/rtorrent/issues

[hyder365]

Definitely don't want to see such a valuable software project rot away.