-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 older ruby 2.1/2.2/2.3 support #2380
Comments
Thanks for opening this issue. |
One year support after EOL is good for me but several popular distributions use EOL version with own patches. So fixed drop timeline is not good for community. |
Of course, we should care about distributions, and we can predict distros EOL thus suggest "plan" to the community, right?
So, I suggest you
|
If current release supports 2.1 and so on, why can’t existing users continue to use it? Why do you need to support forward compatibility for LTS? Surely it’s enough to have a stable branch with security backports, etc. LTS indicates some desire for stability, so does it even make sense that users would want the latest release, or stick to a known good version? |
Thanks for the update. I will probably remove 2.3 support too. |
Nice work! |
Fluentd v1 now works on ruby 2.1 or later but it has several drawbacks.
dig
method: See drop dig_rb and update required ruby version to 2.3 #2372Removing 2.1/2.2 is good for the further development. td-agent and docker images use ruby 2.3 or later so it doesn't break popular environment.
However removing support without the transition period may break user environment. So support 2.1/2.2 until the end of 2019 is better.
UPDATE: Drop 2.3 together. See https://www.fluentd.org/blog/drop-schedule-announcement-in-2019
The text was updated successfully, but these errors were encountered: