> That new upstream version was uploaded at urgency=high the day before > the freeze, with no explanation other than "new upstream release". > Given that 3.4.0 had been out for a fortnight by that point, it looks > very much like trying to game the freeze. :-(
It indeed looks bad. I believe this is just a mistake. FYI, I had a few exchanges with Blair Hester, who is the sponsored person for the upload of 3.4.0, and he feels bad about the current situation, and would like to fix it. James Page, the sponsor for the upload, also expressed his regret. But let's not discuss that, and let's try to fix things in Jessie. > rabbitmq-server maintainers, are there any other RC bugs that you're > planning to file on the package? There's another issue about SSLv3, but considering that this has been disabled from Sid/Jessie, so as Blair Hester wrote, we don't think rabbitmq-server in Debian is affected. I'm not aware of any other issue. Now, seeing that 3.4.0 is in Sid, is it ok to target testing-proposed-updates for 3.3.5-1.1 here? We would also update Sid to 3.4.1 then. Please let me know, and I'll work out with Blair Hester and probably Matt Kraai <kr...@ftbfs.org> to do the actual upload. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54905424.8050...@debian.org
