Unlock/unretire F34 branch in Fedora dist-git because F34 EOL is in May, so maintainers still need to be able to push changes into F34 branches if needed - I've checked several components and all of them have F34 branch already locked, which results into nobody being able to push changes into the branch.
As soon as possible.
Metadata Update from @zlopez: - Issue tagged with: high-gain, medium-trouble, ops
A number of components in PDC have EOL for f34 branch set to today. Script si running to correct it but It will take a while to update all the entries.
Metadata Update from @humaton: - Issue untagged with: high-gain, medium-trouble, ops
Metadata Update from @humaton: - Issue assigned to humaton - Issue tagged with: high-gain, medium-trouble, ops, releng
So, during the branching of F34 wrong EOL was used to create the PDC entries. All of the branches should now be accessible again until the real EOL 05-17-2022
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
https://src.fedoraproject.org/rpms/packit/pull-request/271
I can confirm it works correctly now. Thank you for fixing it so quickly.
Branch F34 in Vim works as well. Thank you for fixing it! :)
Since the release of F36 was delayed, the F34 EOL is now June 7 - see https://bugzilla.redhat.com/show_bug.cgi?id=1991678#c19 . Please enable F34 branches once more, because they are now in close again.
@bcotton It would be great if this was coordinated once the new Fedora is released.
Metadata Update from @zdohnal: - Issue status updated to: Open (was: Closed)
The script is chewing through the PDC entries right now, there is a LOT of them for the whole release so it will take a while.
We could add one more releng task into the schedule right after the final GO/NO-GO. Something like an update soon-to-be EOL release to the correct date in PDC.
@humaton thanks, that would be great :)
https://pagure.io/fedora-pgm/schedule/issue/68
Vim F34 branch works again, so it works for me. If you want to close this after the whole process is finished, feel free to do so.
Thank you again!
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Login to comment on this ticket.