I'd like to have a permission to post the following to any remaining Python 3.7 bug:
Packages that still require Python 3.6 one week before Fedora 29 Beta Freeze ([0]) and their FTBFS bug remains in NEW state, will be mass retired. Packages marked as blocked by non-FTBFS bug are excluded from this. [0] https://fedoraproject.org/wiki/Releases/29/Schedule
I'd post reminders every 3-5 days.
I'd send a package-to-maintainer maintainer-to-package list to devel and the maintainers.
Later, I would retire the packages that fail to respond. I'd communicate this with dependent packages prior to taking action.
Rationale: Those packages will fail to install on Fedora 29. They will block the upgrade from F27 or F28 if installed. I could possibly do a nonrepsonsive maintainer process for all those bugs, but that would be tedious. Consider this a request for exception.
Current list of packages that require Python 3.6 in Fedora 29 (not all meet the criteria for the retirement, some are blocked, some are ASSIGNED):
Thanks.
BTW I was really convinced that I've just sent this request couple minutes ago, but I couldn't find it anywhere, so I might have just closed the tab before doing it or I migth have posted it to some unrelated Pagure repo. If you find a second version of this somewhere, please let me know.
Are any of these needed by packages in the critical path? Are they all leaf nodes? I'm inclined to vote +1 for this proposal, but want to make sure I fully understand the impact.
What about:
Leaf packages that still require Python 3.6 one week before Fedora 29 Beta Freeze ([0]) and their FTBFS bug remains in NEW state, will be mass retired. Packages marked as blocked by non-FTBFS bug are excluded from this. [0] https://fedoraproject.org/wiki/Releases/29/Schedule
+1 to the amended proposal
In the 2018-08-06 FESCo meeting, we agreed to try to get all FESCo members to vote on this ticket (in the ticket here -- let's not wait for the next meeting) as quickly as possible.
I'm +1 to the modified proposal (but would still like to ensure we're not retiring anything listed in the critical path).
In the 2018-08-06 FESCo meeting, we agreed to try to get all FESCo members to vote on this ticket (in the ticket here -- let's not wait for the next meeting) as quickly as possible. I'm +1 to the modified proposal (but would still like to ensure we're not retiring anything listed in the critical path).
I'm +1 to this proposal. Also, if we end up retiring something on the critical path, we will find out very quickly. (This would be a decent canary for discovering whether something is unmaintained in the critical path, also.)
In case you will be retiring python-pygit2, feel free to reassign that to me and I will take care about package.
Leaf packages:
+1
There is a policy in place that allows to retire pkgs with broken deps in general just nobody is doing it.
hug breakage is unrelated to that issue, it's because falcon was updated without announcement ... I will fix it. oslo and openstack clients are being adressed too, but we're in the middle of preparing an OpenStack release.
hug breakage is unrelated to that issue
The breakages happen for various different reasons, not necessarily because Python was updated. Yet all breakages are relevant and their outcome is broken dependencies. If you have some updates about particular packages I suggest to post them in the appropriate bugzillas. Simply setting the bug to ASSIGNED and saying: "We'll deal with this in X days" is OK to prevent the retirement we speak about in this ticket.
One week before Fedora 29 Beta Freeze si in a week from now.
Since this is already the majority, I'm going to proceed with updating the bugs with the agreed text.
I count +7 and it's been more than a week, so this is approved.
Metadata Update from @bowlofeggs: - Issue tagged with: pending announcement
This was announced today.
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.