On 2025-11-06 12:11, Fabio Valentini wrote:
On Wed, Nov 5, 2025 at 8:30 AM Alejandro Sáez Morollón <[email protected]> wrote:


(snip)

Thank you for working on this!

TL;DR: Yes, they would have upgrades, but we might only have 2~3 compat
packages at a given time, and I, personally, think it adds more complexity.

I agree, this seems to just be a complicated middle ground between the
current status quo (major Go update pushed to stable branch) and fully
versioned packages, with the downsides of both, but with the
advantages of neither.

And while I can see the argument that pushing major version updates
for Go to stable branches can cause unintended breakage and churn, I
don't think this would be a big problem in practice. And I assume that
*if* a change to the update cycle for golang like this were
implemented, the update would still land in rawhide *first*, then sit
there for a while (weeks? months?) until all problems have been
resolved, and *only then* merged to stable branches?

Fabio

That's right. Maybe it was not clear in my initial mail, but I am not trying to remove in any way the workflow. Every new major release would land on Rawhide first, build there, and then move into the other releases. Similar to what we have right now but targeting more branches.

Also, I intend to use mass-prebuild [0] before even pushing to Rawhide. It's something that I should do no matter the outcome of the proposal, as I hit/created last-minute issues in the previous two Fedora releases. I played with the tool recently, and I really like it.

As far as I know, we can't run it as part of the CI, but the state of the packages will appear in COPR and I can always link it to the PRs for everyone to see.

[0] https://packages.fedoraproject.org/pkgs/mass-prebuild/mass-prebuild/

--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to