

The ordinary process of making a PR, addressing review feedback, etc. Which is to say, there's not a strict process right now. As a side conversation, how do I follow the 4.0 release process?Ĥ.0.0-beta.1 will be the first release we've had in years - the project was (mostly) dormant for a few years until development spun up again in late 2021.

If there are still hybrid torrents that fail in main then absolutely that should be in 4.0.0Īs far as padding & extended file attributes go, that would be fantastic. This may be failing in 3.00 but AFAIK hybrid torrents are working correctly in main - this is what the transmission-show-bittorrent-v2-hybrid-test test is for? So as far as 3.00 goes I think this issue is a duplicate of #1964? In version 3.00 ( bb6b5a0) opening a hybrid v1+v2 torrent file in transmission-qt results in the error: "invalid or corrupt torrent file".
