> I am eager to revert mistune (and therefore django-hyperkitty) back to > previous versions, and to open bugs against reverse deps, with new > uploads in experimental for both mistune and django-hyperkitty.
this would be great indeed, thanks! > I consider a delay between bug opening and making them RC on the > reverse-deps of a month, which, added to the removal delay, means around > mid-march I'll probably reupload mistune 2.0.0 and django-hyperkitty in > unstable. from what i have seen, many of the downstream projects developers were rather surprised by the sudden release of a mistune 2.0 version, and they were uncertain how to move forward in a proper way, given the vast number of differences and incompatible changes. There also seems to be a complete lack of guidance from mistune upstream on how to port projects from 0.8.x to 2.x: do you think any effort will be spent by mistune upstream to provide any such documentation? without it, i'm afraid 1 month is not enough (anecdotally, the 2.x upload in unstable was a little more than a month ago, and i dont think any upstream project mas ported to it, so that should provide some guidance on how long to wait to make it RC) > Last but not least, do you have appropriate tooling to file bugs against > mistune reverse deps a bit more efficiently than "mail by mail"? `mass-bug` from devscripts -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi