F42 Change Proposal: Automated onboarding to Packit release automation for new packages (system-wide)

Project Discussion Change Proposals
,
21

Will it also be able to trigger such PRs for already imported packages?

I have never gotten around to figure out how to do this, and if you
could automate that for me, I would like to give it a try / look at a PR
how it would be done.

22

This is a good idea and we have briefly discussed it with the team already, it could be definitely done either as a followup or at once, I will make a note about this in the tracked issue (we would need to think about what would be a convenient way for packagers to trigger that).

At the moment, you can at least use a packit CLI command that can generate a config for you as well, see the docs or request your package to be manually onboarded by us via an issue (when discussing, we actually thought about using the automation for creating the PRs for these issues).

23

Thanks Miro. Actually, Rawhide has been our aim but the description did not cover that. Iā€™ve rephrased it. (Our dist-git onboarding script uses Rawhide as a default as well.)

The automation would be configured by default to operate only on rawhide.

The change covers this already.

Side note:
This option might help to allow bigger version jumps (e.g. major/minor) only for Rawhide and e.g. fix releases to other branches. But we can definitely leave this for the maintainer to decide and explicitly change if/when needed.

24

This change proposal has now been submitted to FESCo with ticket #3317 for voting.

To find out more, please visit our Changes Policy documentation.

25

Hi @decathorpe @ngompa @dcantrell @salimma !

I donā€™t want to disturb the voting process too much but I am worried there might be a misunderstanding going on so I would rather mention I few things explicitly so you can vote on the right subject:

  • This change proposes an opt-out workflow to opt-in (via pull request) to the Packit setup. (I.e. maintainer needs to merge the pull request to enable the automation.)
  • The pull request can mention any warnings, rules, suggestions,ā€¦ (e.g. not use for Rust packages)
  • The pull-requst will propose a setup for Rawhide. This, and other things can be changed by the maintainer.

We can also do some service-side filtering if needed.

FrantiŔek

26

This change has been accepted by FESCo for Fedora Linux 42, with the modification that itā€™s just opt-in for F42, as per ticket update. A full list of approved changes to date can be found on the Change Set Page.

To find out more about how our changes policy works, please visit our docs site.