Hello, just a small update. We have verified recently that Packit staging correctly creates F38 updates now: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b3613064bf
This will land in production tomorrow, so as of March 7th, Packit will correctly create F38 dist-git PRs and everything else. Fabio, thank you for giving us a list of missing updates. Maintainers in CC, please update your f38 dist-git branches & provide bodhi updates before the final freeze, Tue 2023-04-04, so that you have up to date versions in Fedora 38 before the release. In my former email, I thought that only bodhi updates are missing. That was incorrect, f38 dist-git branch needs to be updated as well. Tomas On Thu, Mar 2, 2023 at 8:23 PM Tomas Tomecek <ttome...@redhat.com> wrote: > > > On Thu, Mar 2, 2023 at 4:48 PM Miro Hrončok <mhron...@redhat.com> wrote: > >> On 02. 03. 23 16:06, Fabio Valentini wrote: >> > On Thu, Mar 2, 2023 at 3:47 PM Tomas Tomecek <ttome...@redhat.com> >> wrote: >> >> >> >> Hi Fabio, answers inline below. >> >> >> >> On Wed, Mar 1, 2023 at 5:50 PM Fabio Valentini <decatho...@gmail.com> >> wrote: >> >>> >> >>> On Wed, Mar 1, 2023 at 5:34 PM Matej Focko <mfo...@redhat.com> wrote: >> >>> >> >>> - linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38 >> >>> - osbuild-composer v75: submitted to F39, F37, F36, but not F38 >> >>> - cockpit-composer v44: submitted to F39, F37, F36, but not F38 >> >>> - gpxsee v12.1: submitted to F39, F37, F36, but not F38 >> >>> - osbuild v81: submitted to F37, F36, but not F39 or F38 (?) >> >>> - mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38 >> >>> - osbuild-composer v76: submitted to F39, F37, F36, but not F38 >> >> >> >> >> >> Thank you for the list, once we get guidance on how to proceed (see >> below), we will create those missing updates. >> >> >> >>> Whatever the reason, what should be done about the missing updates? >> >>> I'll be publishing my "builds + updates missing from Fedora Branched >> >>> report" soon anyway, so the packages will show up there either way ... >> >> >> >> >> >> We as Packit have honestly the same question: what does this freeze >> exactly mean? Should we continue creating bodhi updates? >> >> >> >> CCing Ben to give us guidance. >> > >> > The fact that a release is currently "frozen" should not affect >> > submission of updates at all. >> > The only difference there is how updates are pushed from "testing" to >> > "stable" state: >> > Updates will not be submitted to "stable" repos automatically after a >> > few days, but only after the freeze is officially lifted. >> > >> > Since packager's cannot "mess this up" (it is enforced by update >> > infrastructure), there is no reason to not build + submit updates for >> > releases that are currently in a "freeze", especially if you are also >> > submitting the updates to stable branches of Fedora. >> >> In other words: It depends. Same as with updates to stable releases. >> >> I'd say that if you are creating the update in stable releases, you >> should also >> create it in frozen/branched. Not doing it creates mess. >> >> However, whether or not an update is suitable for a stable release or for >> a >> post-Beta branched release must always be decided by the packager and >> never by >> a service. >> > > Perfect, thanks for the explanation, Fabio and Miro. > > We will create the missing updates. > > We have already fixed this and it will be rolled out to production on Tue, > 7th. > > >> >> >> >> -- >> Miro Hrončok >> -- >> Phone: +420777974800 >> IRC: mhroncok >> _______________________________________________ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
