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

api-platform: fix maintenance policy and fix eol state of releases #6814

Merged
merged 2 commits into from
Feb 21, 2025

Conversation

lazka
Copy link
Contributor

@lazka lazka commented Feb 21, 2025

  • 3.3 was set to EOL despite being still supported atm
  • 3.2 was never set to EOL despite being EOL since 4.0 was released

the text said that two versions are supported, while the linked upstream policy states that three releases are supported, so adjust the text accordingly.

lazka and others added 2 commits February 21, 2025 07:30
* 3.3 was set to EOL despite being still supported atm
* 3.2 was never set to EOL despite being EOL since 4.0 was released

the text said that two versions are supported, while the linked upstream
policy states that three releases are supported, so adjust the text
accordingly.
Copy link
Member

@marcwrobel marcwrobel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for this fix @lazka !

Took the opportunity to use the term "release" instead of "version" where appropriate.

@marcwrobel marcwrobel added the product-fixes Product content or release fixes that do not count as updates label Feb 21, 2025
@marcwrobel marcwrobel merged commit a8c6952 into endoflife-date:master Feb 21, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product-fixes Product content or release fixes that do not count as updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants