Skip to content

release_and_maintenance.rst: reflect that 2.16 is EOL #2770

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

Draft
wants to merge 1 commit into
base: devel
Choose a base branch
from

Conversation

Andersson007
Copy link
Contributor

release_and_maintenance.rst: reflect that 2.16 is EOL

release_and_maintenance.rst: reflect that 2.16 is EOL
@Andersson007 Andersson007 added backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch backport-2.19 Automatically create a backport for the stable-2.19 branch labels Jun 27, 2025
@Andersson007
Copy link
Contributor Author

ready for review

@samccann
Copy link
Contributor

Holding off on this to verify if 2.16 is official eol'd. usually one core version goes EOL and a new one is created, but 2.19 has been delayed til late July.

@samccann samccann marked this pull request as draft July 10, 2025 19:51
@samccann
Copy link
Contributor

Got confirmation 2.16 eols when 2.19 releases. Putting this in draft for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-2.17 Automatically create a backport for the stable-2.17 branch backport-2.18 Automatically create a backport for the stable-2.18 branch backport-2.19 Automatically create a backport for the stable-2.19 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants