Voting -1. We already have enough issues getting collections to run tests for the current Ansible Core version, so I’m not sure requiring devel or milestone that randomly introduce CI breakages is very helpful. Can we instead make the requirements for testing the latest Ansible Core version (including stable-2.xx ASAP after betas the 2.xx.0 betas start getting released) more strict and properly enforce those requirements?
I guess the
or on a scheduled basis of at least once per week
alternative makes this less disruptive, but I think having voting CI tests against the latest Core release is the most important here and it’s likely that some maintainers will just ignore the non-voting scheduled devel CI runs. I’d probably be willing to change my vote to +1 with this in mind, but there’s already a majority so
.
I think we need to get feedback from collection maintainers that aren’t member so of the Steering Committee, we aren’t representative of the people this is going to impact
If the aim is to ensure that the community ansible package can be released close after the ansible-core release then I think you need to mandate this check in a collection wanting to be included. Otherwise we will get back into the same problem where ansible-core 2.21.0 comes out, ansible 14 needs to ship a new version based on that new core release but only finds out collections x, y, z don’t work is a pretty poor sign of quality. If people want to be included in this package it should be on them to ensure the collection is properly maintained and not the builders of the ansible package to chase people up.
I believe we aren’t repressive here - the included content must be stable and work with upcoming core versions - it’s imo a sane and expected requirement to run checks against devel/milestone at least once a week and in a separate job if maintainers don’t want to pollute PRs with unrelated failures. This is what the change introduces ![]()
As the poll has reached the quorum on approval, I’ve merged the pull request.
Thanks everyone for your great contributions to this effort! I’ll prepare the announcement.