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

Deprecation of v1.1 #688

Merged
merged 1 commit into from
Oct 8, 2024
Merged

Deprecation of v1.1 #688

merged 1 commit into from
Oct 8, 2024

Conversation

mplsmitch
Copy link
Collaborator

Ending support for v1.1, 180 days after the official release of v3.0

What is the proposal?

From the documentation:

Supported versions SHALL NOT span more than two MAJOR versions. Past versions that are beyond the two most recent MAJOR versions will be deprecated 180 days after the latest MAJOR version becomes official.

It's now been 180 days since v3.0 became the official release so v1.1 should be deprecated.

Is this a breaking change?

  • [x ] No

Which files are affected by this change?

README and version v1.1

Ending support for v1.1, 180 days after the official release of v3.0
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

@richfab richfab left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you @mplsmitch!

@richfab richfab merged commit 4840025 into master Oct 8, 2024
1 check passed
@richfab richfab deleted the mplsmitch-patch-1 branch October 8, 2024 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants