-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
End-of-life for JRuby 1.7.x #4112
Comments
So where is the JRuby 10000 or JRuby 10.0.0.0 |
So far, the things that are keeping us from moving are: #3928 , #3922 , #3921 , and the significantly increased memory overhead. Some of those things we may be able to work around, and it's possible we'll stumble onto a few more things after we get past those. Hoping to be able to pick back up on our efforts to explore the upgrade in the next month or two. |
9k not yet running on AIX: #3495 |
I know it's not your problem, but..... Since Torquebox 4 hasn't been released yet, and does not have all the features of Torquebox 3.x it would be great if Torquebox 3.x shipped with JRuby 9000 https://issues.jboss.org/browse/TORQUE-1259 |
Thank you all for the hard work you put into this project! It is much appreciated. Currently, this one is blocking us from moving to 9.1.3.0 #4124 |
#4124 has been fixed for 9.1.4.0. |
Candidate for inclusion is #1183, too. |
#4365 prevents 9.1.x.x from being a viable candidate for use in production under OpenJDK 7. Is JRuby's official support going to move to 8 and above? |
Could we get #4389 to 1.7-branch? We're not quite ready to step to 9.x branch but this would make it possible to include JRuby as a dependency instead of needing to distribute it separately to each installation. |
@jmiettinen I don't see why not. I know @kares had a revision, so I'll dig that up and merge that too. |
Is there an actual end-of-life date defined for JRuby 1.7.x by now? The initially given date (end of 2016) is obsolete. We need this info in order to decide whether and when we need to migrate. |
@obfuscoder the last (planned) release for JRuby 1.7.x has already happened on May/2017 |
Thanks for theinfo. One small follow up question tho: Will there still be fixes and releases for the 1.7.x branch for newly found security issues or won't even those issues be fixed? |
@obfuscoder It is our intent to not release any more but if it was devastatingly bad security issue we may end up releasing it just to not leave anyone hanging. Thankfully, we have had very few CVEs to deal with over the years so fingers crossed...openssl is the most likely target for security problems in Ruby and that is still being maintained with backwards compat in mind (for now anyways). If an openssl problem was found then any legacy production envs could update that gem. |
JRuby 1.7.27 appears to be sufficient as a last release for 1.7. We shall call 1.7 officially EOL now. |
see jruby/jruby#4112 for context on jruby 1.7 reaching EOL.
Upstream changes (from CHANGELOG.md): ## 1.10.0 / 2019-01-04 ### Features * [MRI] Cross-built Windows gems now support Ruby 2.6 [#1842, #1850] ### Backwards incompatibilities This release ends support for: * Ruby 2.2, for which [official support ended on 2018-03-31](https://www.ruby-lang.org/en/news/2018/06/20/support-of-ruby-2-2-has-ended/) [#1841] * JRuby 1.7, for which [official support ended on 2017-11-21](jruby/jruby#4112) [#1741] ### Dependencies * [MRI] libxml2 is updated from 2.9.8 to 2.9.9 * [MRI] libxslt is updated from 1.1.32 to 1.1.33 ## 1.9.1 / 2018-12-17 ### Bug fixes * Fix a bug introduced in v1.9.0 where `XML::DocumentFragment#dup` no longer returned an instance of the callee's class, instead always returning an `XML::DocumentFragment`. This notably broke any subclass of `XML::DocumentFragment` including `HTML::DocumentFragment` as well as the Loofah gem's `Loofah::HTML::DocumentFragment`. [#1846] ## 1.9.0 / 2018-12-17 ### Security Notes * [JRuby] Upgrade Xerces dependency from 2.11.0 to 2.12.0 to address upstream vulnerability CVE-2012-0881 [#1831] (Thanks @grajagandev for reporting.) ### Notable non-functional changes * Decrease installation size by removing many unneeded files (e.g., `/test`) from the packaged gems. [#1719] (Thanks, @stevecrozz!) ### Features * `XML::Attr#value=` allows HTML node attribute values to be set to either a blank string or an empty boolean attribute. [#1800] * Introduce `XML::Node#wrap` which does what `XML::NodeSet#wrap` has always done, but for a single node. [#1531] (Thanks, @ethirajsrinivasan!) * [MRI] Improve installation experience on macOS High Sierra (Darwin). [#1812, #1813] (Thanks, @gpakosz and @nurse!) * [MRI] Node#dup supports copying a node directly to a new document. See the method documentation for details. * [MRI] DocumentFragment#dup is now more memory-efficient, avoiding making unnecessary copies. [#1063] * [JRuby] NodeSet has been rewritten to improve performance! [#1795] ### Bug fixes * `NodeSet#each` now returns `self` instead of zero. [#1822] (Thanks, @olehif!) * [MRI] Address a memory leak when using XML::Builder to create nodes with namespaces. [#1810] * [MRI] Address a memory leak when unparenting a DTD. [#1784] (Thanks, @stevecheckoway!) * [MRI] Use RbConfig::CONFIG instead of ::MAKEFILE_CONFIG to fix installations that use Makefile macros. [#1820] (Thanks, @nobu!) * [JRuby] Decrease large memory usage when making nested XPath queries. [#1749] * [JRuby] Fix failing tests on JRuby 9.2.x * [JRuby] Fix default namespaces in nodes reparented into a different document [#1774] * [JRuby] Fix support for Java 9. [#1759] (Thanks, @Taywee!) ### Dependencies * [MRI] Upgrade mini_portile2 dependency from `~> 2.3.0` to `~> 2.4.0`
* Add useful links for maintenance * Add EOL note on Ruby 2.3 * Remove MRI 2.0, 2.1 and 2.2 (long EOL) This will save build time & allow me to use new features. * Remove JRuby 1.7 (EOL) jruby/jruby#4112 (comment) * Attempt to use X.Y versions to allow automatic upgrade * Add useful note to check JRuby versions * Update documentation & changelog * Stop testing for Ruby 2.2 on Windows * Test on Ruby 2.6 (Windows)
* Add useful links for maintenance * Add EOL note on Ruby 2.3 * Remove MRI 2.0, 2.1 and 2.2 (long EOL) This will save build time & allow me to use new features. * Remove JRuby 1.7 (EOL) jruby/jruby#4112 (comment) * Attempt to use X.Y versions to allow automatic upgrade * Add useful note to check JRuby versions * Update documentation & changelog * Stop testing for Ruby 2.2 on Windows * Test on Ruby 2.6 (Windows)
We currently plan to end our support for JRuby 1.7 at the end of 2016. We believe JRuby 9k has reached a stability and compatibility level that meets (and usually exceeds) JRuby 1.7, and maintaining two major versions is a real headache.
However, we are realistic, and we know there will be outstanding issues for people migrating from 1.7 to 9k. This bug is a placeholder for users to link all their blocking 9k items, so we can have them all in one place.
The sooner we gather these bugs, the sooner we can work toward having a 9k release that's a viable target for all current JRuby 1.7 users.
A few issues we will not be addressing:
Other issues, we'll deal with on a case-by-case basis. Please let us know what's keeping you from migrating to JRuby 9k.
The text was updated successfully, but these errors were encountered: