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

Support for ansible-core versions 2.11 and 2.12 will be dropped in v5.0.0 #340

Closed
briantist opened this issue Jan 8, 2023 · 0 comments · Fixed by #366
Closed

Support for ansible-core versions 2.11 and 2.12 will be dropped in v5.0.0 #340

briantist opened this issue Jan 8, 2023 · 0 comments · Fixed by #366
Assignees
Labels
breaking-change Describes current or future breaking changes
Milestone

Comments

@briantist
Copy link
Collaborator

briantist commented Jan 8, 2023

SUMMARY

2.11 is EoL already, and 2.12 will be EoL right around when v5.0.0 is released, which should be around May 2023.

What this means

  • We will no longer test against these versions in CI.
  • New and existing code will not be required to support these.
  • Code that currently exists solely to support these versions may be removed in this release, or at a later time.
  • PRs proposed to (re)add compatibility with these versions will be considered if the changes have full test coverage (it still will not be tested against the EoL versions, but it must be tested and working against current versions), and if the changes do not make future maintenance harder. Each will be considered on a case-by-case basis and may not be accepted.
  • Requests to (re)add compatibility with unsupported versions will be closed. Only an actual contribution of such a change will be considered.
@briantist briantist self-assigned this Jan 8, 2023
@briantist briantist pinned this issue Jan 8, 2023
@briantist briantist added this to the v5.0.0 milestone Jan 8, 2023
@briantist briantist added the breaking-change Describes current or future breaking changes label Mar 5, 2023
@briantist briantist unpinned this issue May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Describes current or future breaking changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant