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 to six months support, rather than n-1 #1114

Merged
merged 1 commit into from
Dec 7, 2019

Conversation

shadowspawn
Copy link
Collaborator

Pull Request

Problem

I had said we should support the current major version and the previous major version. But I realise now that does not work very well when we have close major releases, like we did with v3 and v4 to clear the backlog of Pull Requests.

Solution

I suggest instead we support old versions from six months from when the new version is released. Then if we release new major versions fast then users of older versions still get time to upgrade, and if it is a long time between major releases we do not support the old version indefinitely.

@shadowspawn
Copy link
Collaborator Author

We could support for longer than six months if you would like @abetomo. I had a quick look around and did not find any security policy on the products I looked at to compare!

Copy link
Collaborator

@abetomo abetomo left a comment

Choose a reason for hiding this comment

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

👍

@abetomo abetomo merged commit 45d371e into tj:develop Dec 7, 2019
@shadowspawn shadowspawn deleted the feature/support-six-months branch December 7, 2019 04:32
@shadowspawn shadowspawn added the pending release Merged into a branch for a future release, but not released yet label Dec 11, 2019
@shadowspawn shadowspawn removed the pending release Merged into a branch for a future release, but not released yet label Jan 6, 2020
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.

2 participants