`Braid::Operations::Proxy::exec` deadlock when subprocess writes too much to stderr about braid HOT 3 CLOSED

As to which ruby versions we support. I would probably stop supporting any the ruby team has determined to be "obsolete" or unsupported. Looking at wikipedia page https://en.wikipedia.org/wiki/Ruby_(programming_language) it seems that 2.2 is no longer "supported" but will still receive security patches till "2018-03-31". I would be inclined to peg it as our supported release but if you require something from 2.3 maybe that would be acceptable to be our latest supported version.

Which reminds me. I think I need to redeploy all my works rubies ;)

Thoughts?

from braid.

Ruby MRI 2.2 is more than enough for anything I've wanted to use so far, so it sounds good to me. Are we supporting JRuby? The Travis CI configuration currently includes jruby-19mode. Is there a simple correspondence between JRuby and Ruby MRI versions, or do we need to pick a minimum JRuby version and then check that each feature we want to use is available in both our minimum Ruby MRI version and our minimum JRuby version?

from braid.

It has been a while since we have used jruby but I would guess that you can probably just rely on modernish version of ruby 9000 line. People using it seem to update reasonably regularly.
Perhaps as far back as 9.1.1.0 or maybe just back to 9.1.3.0

Not sure. Also not sure if we have any commandline users using jruby

from braid.