Bug 204933 - [PATCH] Upgrade lang/jruby to 1.7.23
Summary: [PATCH] Upgrade lang/jruby to 1.7.23
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ruby (Nobody)
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2015-12-01 14:21 UTC by Andrew Smith
Modified: 2016-12-07 08:28 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (ruby)


Attachments
1.7.22 to 1.7.23 diff (235.82 KB, patch)
2015-12-01 14:21 UTC, Andrew Smith
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Smith 2015-12-01 14:21:59 UTC
Created attachment 163705 [details]
1.7.22 to 1.7.23 diff

diff against 1.7.22 (previous) version

http://jruby.org/2015/11/24/jruby-1-7-23

Relevant release notes
* Various jar and/or classpath fixes with filesystem-related methods
* 31 issues fixed for 1.7.23
Comment 1 Steve Wills freebsd_committer freebsd_triage 2016-12-06 19:01:28 UTC
Sorry for the long delay, looks like jruby was updated in the mean time. I've gone ahead and updated to the latest and greatest, 9.1.6.0, in r427982. Hopefully this makes up for the delay on this PR in some way. :)
Comment 2 Andrew Smith 2016-12-06 19:09:24 UTC
Whilst the update to jruby 9K is appreciated, one should note the major architectural changes between 1.7.x and 9K.

jruby.org explicitly maintains to distributions, perhaps maybe not for too long, however, for anybody running prod code they may definitely want to stay on the 1.7.x codebase and take the incremental changes before jumping across to 9K because it uses a lot more native code and potentially introduces regressions that need to be tested out on an individual basis over a period.

I recommend, if possible, make a 1.7 and 9K separate port if you are keen to bringing 9K to ports.
Comment 3 Steve Wills freebsd_committer freebsd_triage 2016-12-07 00:21:51 UTC
(In reply to Andrew Smith from comment #2)
According to the JRuby folks I talked to 1.7.x is End of Life at the end of the year, so I thought the quarterly branch should cover the need for 1.7.x until then and there wouldn't be a need for separate 1.7.x and 9.x ports. Sound OK?
Comment 4 Andrew Smith 2016-12-07 08:28:11 UTC
EOL at the end of the year?

There's nothing to that effect in the News feed on the JRuby site and folks might have to spend months on regression testing for large projects, particularly if they are embedded.

I suspect that even when 1.7.x does go EOL it may well end up being like node 0.10 for a long time.