Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change in process for ansible-test platform updates #69

Open
mattclay opened this issue Apr 2, 2024 · 1 comment
Open

Change in process for ansible-test platform updates #69

mattclay opened this issue Apr 2, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@mattclay
Copy link

mattclay commented Apr 2, 2024

Starting with the ansible-core 2.18 development cycle, we're simplifying the process we use to add and remove platforms and versions to the devel version of ansible-test:

  • Changes will no longer be announced here in advance. The changes will still receive changelog entries. The currently available list of platforms and versions can be found in the ansible-test completion files.
  • Removal of old versions should occur at the same time new versions are added. Previously, new versions were added at least two weeks before the version they were replacing would be removed.

If a predictable schedule is required for potentially breaking changes, collection maintainers can switch from testing against the devel branch to the milestone branch.

@felixfontein felixfontein added the documentation Improvements or additions to documentation label Apr 2, 2024
@felixfontein
Copy link
Contributor

I created #70 to discuss this.

@ansible-collections ansible-collections locked as resolved and limited conversation to collaborators Apr 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants