People present: @MariaAga (chair), @ezr-ondrej (notes), @lzap, @Shimon_Shtein, @aruzicka
Discussions
Add Breaking change label
@nadjaheitmann had bring up, that it would help plugin maintainers if we could label PRs that might have break plugins.
- This is impossible to cover completely as we do not have clear stable plugin API, so doing this will always be best effort only
- It won’t hurt to label PRs we think are breaking change as such
- @lzap brought up that it would be better to have regular tests that would reveal plugin breakage
- It was generally agreed that best way for plugins is to setup scheduled testing and thus they will be able to narrow down the time window of the breakage and that would be much more reliable source then PR labels
- Plugins setup in our Jenkins from plugin template do have this out of the box and it would be the best to double down on this effort for all plugins
- AI: @ezr-ondrej will add the tag and we will try to mark PRs that we feel may break plugins, but there are no promises and plugin maintainers should still setup regular testing job.
Cherry-picks
- 3.2
- features, but safe and probably appreciated by community
- Add Safemode Jail for ActiveSupport::TimeWithZone by ludovicus3 · Pull Request #9017 · theforeman/foreman · GitHub
- Add support skipping puppet setup explicitly by jadestorm · Pull Request #9086 · theforeman/foreman · GitHub
- Fixes #34498 - added RHEL9 and CentOS9 Guest OSes by snagoor · Pull Request #9116 · theforeman/foreman · GitHub
- features, but safe and probably appreciated by community
- 3.1
PR assignment
- Security issue, that needs to be addressed ASAP Fixes #34573 - encrypt DSL setting values by ezr-ondrej · Pull Request #9139 · theforeman/foreman · GitHub
- Rest was regular PR assignment