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