> On Sun, Jun 18, 2023 at 09:16:28AM +0000, Mattia Verga via devel wrote:
>
> So one alternative is *not* to push the change to all branches.
>
> Unless it's really necessary, such as fixing an essential bug, I tend
> to leave older Fedora branches on a stable release, to reduce churn
Exactly. Blindly pushing to all active releases is never a good idea. Now, I'm not saying people here do that, but those shortcuts make it too easy to do it in a rash ...
In particular: Most proposals do it in the wrong order (old to new) and some without error catching. You may end up with newer builds in older releases - without an update yet, granted, but still.
> ...
>
> (Also note 'fedpkg clone -B' option to use a separate subdirectory for
> each branch, much more intuitive IMHO.)
That creates a bunch of unrelated git repos. Maybe we should teach fedpkg to use current git's method for that, which is worktrees. That way you share not only the object store ("one fetch rules them all") but also config such as remote definitions (for forks) etc. The main worktree could be a main/rawhide checkout.
Michael
_______________________________________________
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
