On 8/10/25 16:43, Fabio Valentini wrote:
On Sun, Aug 10, 2025 at 12:45 AM Orion Poplawski <orion@xxxxxxxx> wrote:
My recollection is that having unmerged side tags around the release
branch time can be an issue. Is my memory correct?
Yes, this is a problem, since open side-tags could only get merged
into the new "branched" release, but not into rawhide - making it
impossible for the update to actually land where originally intended
(rawhide).
I'm a little confused about this. Presumably updates filed now are
intended to go into F43. Is there anything that would prevent such
updates from landing in F43?
Sure, the packages would also have to be built for rawhide after branch,
but while that might not be top of mind for packagers, but is there
really anything that would prevent that?
I thought I had experienced something that made one throw away the
builds and update completely and start over for both the branched and
rawhide releases.
Are there critical points where side tags updates should be complete by?
The bodhi update needs to land in "stable" before the mass branching
process starts.
Additionally, all bodhi updates that are not "stable" (i.e. due to
failing gating tests) at mass branching time should also get unpushed
- since package maintainers will need to manually fix them up to
correctly land in *both* rawhide *and* branched (after fixing the
problems that broke the packages' gating tests, of course). Note that
this doesn't only affect updates from side-tags, but *all* updates
that are stuck in rawhide's "testing" state due to failed gating
tests.
Fabio
This sounds more familiar - that stuck updates could not get unstuck for
the branched release.
Thanks for the response.
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxx
Boulder, CO 80301 https://www.nwra.com/
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
