#244 drop or de-emphasize the upgradepath checks
Closed: Fixed 3 years ago Opened 3 years ago by kparal.

Reported as taskotron/taskotron-trigger#45 from @kevin:

In the past, upgrade path was very important for Fedora, because you needed newer Fedora releases to have all packages "newer" than the older releases for upgrades. However, now it's not as important, since the recommended upgrade method (dnf system-upgrade) uses 'distro-sync' instead of just upgrade, and even the secondary non recommented upgrade path is just using dnf distro-sync yourself.

This check often has problems when a branched release is in freeze before Beta or Final releases, as updates in older releases go out but updates for branched are frozen pending the milestone.

Since this check isn't that important now, can we drop it or at the very least change it to warning/low priority in the interface? Thanks.


Project page and wiki received a deprecation note:
https://pagure.io/taskotron/task-upgradepath
https://fedoraproject.org/wiki/Taskotron/Tasks/dist.upgradepath

@frantisekz removed upgradepath from trigger_rules and deployed the change.

A greenwave ticket is here:
https://pagure.io/greenwave/issue/110

A bodhi ticket is here:
https://github.com/fedora-infra/bodhi/issues/2077

A fmn pull request is here:
https://github.com/fedora-infra/fmn/pull/269

I believe that's everything needed from our side and we can close this ticket now.

Metadata Update from @kparal:
- Issue close_status updated to: Fixed

3 years ago

Login to comment on this ticket.

Metadata