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

Drop support for 1.x.y releases (EoL stable-1 branch)? #543

Closed
felixfontein opened this issue Dec 31, 2022 · 4 comments
Closed

Drop support for 1.x.y releases (EoL stable-1 branch)? #543

felixfontein opened this issue Dec 31, 2022 · 4 comments
Labels

Comments

@felixfontein
Copy link
Collaborator

SUMMARY

We are currenly releasing 3.x.y releases, and we're still backporting fixes to 2.x.y and 1.x.y. 2.0.0 has been released in October 2021, and I'm not sure whether anyone is still using 1.x.y. (I haven't seen any bug reports for it.)

What do you think about declaring stable-1 End of Life and stop updating it (and removing it from the weekly CI)? If you don't think it should be done soon, when do you think it's time for it?

ISSUE TYPE
  • Admin
COMPONENT NAME

collection

@felixfontein
Copy link
Collaborator Author

As a general policy: how about 'supporting' only the latest two branches (i.e. main and the latest stable-x) and making all other stable branches EOL? That would mean that stable-2 would become EOL once stable-3 is created and 4.0.0 released, etc.

@felixfontein
Copy link
Collaborator Author

I guess everyone seems to be happy with making stable-1 EOL, then. I'll implement that soon.

@felixfontein
Copy link
Collaborator Author

#572 implements this (resp. the first part).

@felixfontein
Copy link
Collaborator Author

1.10.15 has been released, everything removed. Thanks everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant