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

Closed
headius opened this Issue Aug 24, 2016 · 15 comments

Comments

Projects
None yet
@headius
Member

headius commented Aug 24, 2016

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:

  • JRuby 9k releases will always support the most-current Ruby version, give or take a version. We will not support 1.8.7, 1.9.3, 2.0, 2.1, or 2.2-specific behavior in any future releases, and once we have Ruby 2.4 support we will no longer support Ruby 2.3-specific behavior.
  • JRuby 9k supports Java 7 and higher at present, and we will not work to support earlier versions of Java or the JDK. The one exception would be Android, if we can figure out a way to use the Java 7 features we need there. We may drop Java 7 support some time after Java 9 is released.

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.

@netroby

This comment has been minimized.

netroby commented Aug 25, 2016

So where is the JRuby 10000 or JRuby 10.0.0.0

@kares kares referenced this issue Aug 25, 2016

Closed

Java 9 support #4111

2 of 2 tasks complete
@cprice404

This comment has been minimized.

Contributor

cprice404 commented Aug 25, 2016

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.

@ssteidte

This comment has been minimized.

ssteidte commented Aug 26, 2016

9k not yet running on AIX: #3495

@tbeauvais

This comment has been minimized.

tbeauvais commented Aug 27, 2016

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

@creddy

This comment has been minimized.

creddy commented Aug 31, 2016

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

@headius

This comment has been minimized.

Member

headius commented Aug 31, 2016

#4124 has been fixed for 9.1.4.0.

@headius

This comment has been minimized.

Member

headius commented Sep 8, 2016

Candidate for inclusion is #1183, too.

@JasonLunn

This comment has been minimized.

JasonLunn commented Feb 18, 2017

#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?

tuzz added a commit to reevoo/sitemap_check that referenced this issue Mar 13, 2017

tuzz added a commit to reevoo/sitemap_check that referenced this issue Mar 13, 2017

@jmiettinen

This comment has been minimized.

Contributor

jmiettinen commented Apr 26, 2017

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.

@headius

This comment has been minimized.

Member

headius commented May 4, 2017

@jmiettinen I don't see why not. I know @kares had a revision, so I'll dig that up and merge that too.

@obfuscoder

This comment has been minimized.

obfuscoder commented Jul 28, 2017

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.

@kares

This comment has been minimized.

Member

kares commented Jul 28, 2017

@obfuscoder the last (planned) release for JRuby 1.7.x has already happened on May/2017
some jruby-openssl gem releases will still support some of the latest 1.7.x for a while but no JRuby releases are planned at this point.

@obfuscoder

This comment has been minimized.

obfuscoder commented Jul 30, 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?

@enebo

This comment has been minimized.

Member

enebo commented Jul 31, 2017

@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.

@headius

This comment has been minimized.

Member

headius commented Nov 21, 2017

JRuby 1.7.27 appears to be sufficient as a last release for 1.7. We shall call 1.7 officially EOL now.

@headius headius closed this Nov 21, 2017

flavorjones added a commit to flavorjones/concourse-gem that referenced this issue Sep 15, 2018

remove jruby 1.7 and add jruby 9.2
see jruby/jruby#4112 for context on jruby 1.7
reaching EOL.

havenwood added a commit to postmodern/ruby-versions that referenced this issue Dec 6, 2018

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue Jan 12, 2019

tsutsui
ruby-nokogiri: update to 1.10.0.
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`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment