Latest upstream release: 2021.10 Current version/release in rawhide: 2021.10-0.7.rc5.fc36 URL: https://www.denx.de/wiki/U-Boot/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/5022/
Created attachment 1829129 [details] [patch] Update to 2021.10 (#2010449)
the-new-hotness/release-monitoring.org's scratch build of uboot-tools-2021.10-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=76693036
FEDORA-2021-b1079b7042 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b1079b7042
Proposed as a Blocker for 35-final by Fedora user pbrobinson using the blocker tracking app because: I don't remember which pointless process we go through each cycle for this and whether the process writers put this in the Blocker or FE bucket but we need this in GA
What's the impact of not having this in the GA? I voted +1 for a freeze exception, but I don't have enough information to have an opinion on blocker status.
(In reply to Ben Cotton from comment #6) > What's the impact of not having this in the GA? I voted +1 for a freeze > exception, but I don't have enough information to have an opinion on blocker > status. Well: 1) there's at least a number of fixes in it compared to the one that's currently GA (still more platforms to be verified, not saying we won't need more fixes). 2) people file bugs when U-Boot isn't a GA release and it adds a bunch of support effort for the entire stable release cycle. See all the previous releases where we've done this, pretty much every recent cycle as the release day generally falls the day before freeze, so there's plenty of precedent for this
(In reply to Peter Robinson from comment #7) > See all the previous releases where we've done this, pretty much every > recent cycle as the release day generally falls the day before freeze, so > there's plenty of precedent for this Peter, this is the uboot upstream release cycle vs. Fedora's? I wonder if we have any chance of influencing that to be more aligned (as we were able to do with e.g. Python).
FEDORA-2021-b1079b7042 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b1079b7042` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b1079b7042 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Well there's a whole list of criterion for blocking reference in the required justification requirement sections of the blocker app's proposal page. https://fedoraproject.org/wiki/Basic_Release_Criteria https://fedoraproject.org/wiki/Fedora_35_Beta_Release_Criteria https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria Without a justification, it's not a blocker. If this were a GRUB request to bump, I'd vote no. Something has to be broken in some way. That users file bugs because it's not an upstream release version isn't a good enough justification.
-3 blocker / +3 FE in https://pagure.io/fedora-qa/blocker-review/issue/508 , marking as such.
FEDORA-2021-b1079b7042 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.