[Pkg-mailman-hackers] Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies

[Pierre-Elliott Bécue]

Pierre-Elliott Bécue <peb at debian.org> wrote on 09/01/2022 at 13:11:41+0100:

> [[PGP Signed Part:Good signature from 29BFA0D079290ACA Pierre-Elliott Bécue <becue at crans.org> (trust ultimate) created at 2022-01-09T13:14:08+0100 using RSA]]
>
> Sandro Tosi <morph at debian.org> wrote on 09/01/2022 at 03:38:18+0100:
>
>>> 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.
>
> Well, having participated to writing some documentation, I am not sure
> that this number of differences is that vast. Mistune, on itself, was
> not that big a project in terms of features, and getting a grip on the
> new version should not take that much time.
>
>> 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)
>
> Okay, lets go with 3 months from Jan the 15th so April the 15th. If
> things seem to go faster than expected I will maybe contract that
> schedule. (let's say if two thirds of the deps are up-to-date upstream
> on March the 1st I'll come back to the initial schedule)
>
> Would that make sense for you?
>
>>> 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
>
> Ah right, I never used it, it's about time. :)
>
> Thanks!

Done, I'll mass-bug this evening.

I plan to reupload immediately 2.0.0 in experimental. This means no
further upload of mistune 0.8.4 are possible in unstable. Is this okay
with both of you?

Cheers!

-- 
PEB