-
Notifications
You must be signed in to change notification settings - Fork 101
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
Announce 3.x EOL after Jetty's End of Community Support #453
Comments
It's now August 20 so we are pretty much running an EOL version? I just downloaded 3.0.0 😮💨 |
You can expect the release in the next days after I get final feedback from ORF ON people. Until then you can test the release candidate e.g. via the provided Docker images. |
I have the impression that ringo is only maintained for backward compatibility purpose only, for the needs of the corporates invested in it and don't want to move to new technologies but not for new users. The evidence is no one cares about this repo, no one cares and answers submitted issues and there is no new features added. This is a dead project. |
If you have projects running on top of Ringo, feel free to join the development & new ideas. The overall progess is depending on the underlying JavaScript engine Rhino. Since the whole core team is working for @orfon, it is no surprise that the main focus of the project is aligned with them. |
Btw. We will release 4.0.0 together with the switch of the RingoJS.org server. This will also replace old Google Groups and IRC logs and you can start discussions and questions in our project's Github Discussions. |
Jetty 9.x will be End of Community Support and more or less EOL starting this June. We should ship RingoJS 4.0.0 before this date. See: jetty/jetty.project#7958
The text was updated successfully, but these errors were encountered: