On 7.4.2018 15:53, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, Apr 06, 2018 at 10:33:04AM -0500, Jason L Tibbitts III
> To be completely honest, if someone wants to drop a python2 subpackage,
> that's their prerogative but it does bring up an interesting question.
> Normally if someone wants to orphan a package, they're welcome to do so
> and others are welcome to pick it up. But this is about removing a
Yes, but as with any removal action, it behooves the maintainer to
query and think if that removal will not cause disruption, and if it
will, what is the best way to proceed (announce more widely, warn and
delay the removal, postpone indefinitely?).
So apparently the general confusion/problem here is lack of
communication when removing python2-subpackages.
Filling a Fedora Change proposal for every single python2 subpackage
removal feels a bit overengineered. So let's set up some basic rules
about what to do when a python2 subpackage is being removed. E.g. do it
in rawhide only, send an announcement do devel, wait X days, etc.