This is a tracking bug for Change: Mass Python 2 Package Removal
For more details, see: https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
(Sub-)packages only providing python2 importable modules without additional functionality will be removed from Fedora unless some other package(s) depends on them.
According to the Fedora 30 schedule, today is the deadline for changes to be in a testable state. If your change is ready to be tested, please set the status to MODIFIED. If you know your change will not be ready for Fedora 30, you can set the version to rawhide and notify firstname.lastname@example.org. For more information about this milestone, see the Changes Policy.
Thanks for the reminder, Ben. This was testable from the beginning and it is testable now. It is a work in progress and we would like to continue.
We can either:
1) mark this done and submit the same thing for F31
2) "move" this to F31
3) say that this was done for F30 and that the rules apply further for F31 as well
I honestly don't know and I don't want to bother FESCo, but I think FESCo is the only body that can decide.
In my opinion, I would say option 3 is the most accurate. Given the nature of the change, I don't think it's necessary to escalate this to FESCo. If some python2 packages don't get removed by the deadline, I don't think anyone will be surprised if they get removed in F31.
Makes sense. What's the BZ status then?
You can either go with MODIFIED for now, or jump ahead to ON_QA and get ahead of the Code Complete (100%) milestone in a few weeks. Whichever you feel is more appropriate for the current state of the work.
There are things I'd like to add for f31, so I'll submit a new change.
For now, the rules practically apply for F31 as well. (If anyone formally disagrees, we can formally wait for the new change.)
We have reached the Code Complete (100%) milestone in the Fedora 30 development cycle. At this point, all Changes should be fully code complete and ready for testing during the beta freeze. If your Change has reached this milestone, please set the status to ON_QA. If it has not, this Change will be submitted to FESCo to evaluate the contigency plan and decide if the Change will continue in the Fedora 30 cycle.