Process for dealing with cherry picks

Just to close this out, I’ll summarize what is now happening in practice.

Every week for Foreman core there’s the maintainers meeting. They go over all merged PRs since the last meeting and decide for every PR if it needs the cherry pick.

It’s also possible to explicitly nominate a cherry pick by adding the Needs cherrypick. It’s not exactly formal, but it does help if you add which versions it should be picked to. During the same weekly maintainers meeting this gets reviewed and picked.

It should be noted that that only covers core. There’s also a weekly release team meeting which also makes sure that issues are picked. This is more Redmine driven.

If anyone not part of these teams wants to make sure a fix gets into a (supported) release, it can be added to the release team agenda:

If there’s additional concerns, we can always revise the plan but I think we have a decent enough process in place to make sure cherry picks happen and don’t rely on a single person. With that, I consider this RFC as resolved.

Thanks everyone involved!

1 Like