[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737323#comment-16737323 ] Sean Busbey commented on AVRO-1559: --- I agree for 1.9.0+ we should bump to 2.3+. IIRC JRuby's current versions also support those ruby versions so we should be good. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Apache Avro > Issue Type: Wish > Components: ruby >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen >Priority: Major > Fix For: 1.9.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737324#comment-16737324 ] Sean Busbey commented on AVRO-1559: --- still worth a DISCUSS thread on dev@avro, since there are some more Ruby folks floating around there now. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Apache Avro > Issue Type: Wish > Components: ruby >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen >Priority: Major > Fix For: 1.9.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737259#comment-16737259 ] Tim Perkins commented on AVRO-1559: --- Is it worth revisiting the question of supported Ruby versions for a Avro 1.9.0 release? At the time I'm writing this comment, Ruby 2.2 and earlier are no longer maintained. I'm in favor of only supporting Ruby 2.3 (released 2015-12-25) and later, and explicitly testing against all the supported Ruby versions in the build. It seems unlikely to me that somebody would be willing to accept a major Avro update while being unwilling to update Ruby. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Apache Avro > Issue Type: Wish > Components: ruby >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen >Priority: Major > Fix For: 1.9.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[
https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110763#comment-15110763
]
Martin Kleppmann commented on AVRO-1559:
{quote}
I'm happy to start a Ruby 2.2+ gem along-side the current 1.9+ one so that we
can have a more controlled deprecation period.
{quote}
I'm not aware of any compelling reason to start a new gem. The current
implementation supports Ruby 1.9-2.2 without problem, and I don't think 1.9
support is holding it back.
> Drop support for Ruby 1.8
> -
>
> Key: AVRO-1559
> URL: https://issues.apache.org/jira/browse/AVRO-1559
> Project: Avro
> Issue Type: Wish
>Affects Versions: 1.7.7
>Reporter: Willem van Bergen
>Assignee: Willem van Bergen
> Fix For: 1.8.0
>
> Attachments: AVRO-1559.patch
>
>
> - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore.
> - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a
> recent OSX, it won't compile without manual fiddling).
> - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8.
> Supporting both at the same time adds a lot of overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110757#comment-15110757 ] Sean Busbey commented on AVRO-1559: --- for example, [JRuby 1.7.24|http://jruby.org/2016/01/20/jruby-1-7-24] literally came out yesterday. It still supports Ruby 1.9 and it does not support any of the Ruby 2.y versions. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[
https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110751#comment-15110751
]
Sean Busbey commented on AVRO-1559:
---
{quote}
If we're going to drop support for Ruby versions anyway, we should drop support
for 1.9 as well because it is also EOL, and will no longer receive security
fixes.
{quote}
That's not a sufficient reason for us to drop support, since there easily can
still be folks relying on it that would like newer versions of Avro.
If there are ways that supporting Ruby 1.9 is holding us back, I'm happy to
start a Ruby 2.2+ gem along-side the current 1.9+ one so that we can have a
more controlled deprecation period.
> Drop support for Ruby 1.8
> -
>
> Key: AVRO-1559
> URL: https://issues.apache.org/jira/browse/AVRO-1559
> Project: Avro
> Issue Type: Wish
>Affects Versions: 1.7.7
>Reporter: Willem van Bergen
>Assignee: Willem van Bergen
> Fix For: 1.8.0
>
> Attachments: AVRO-1559.patch
>
>
> - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore.
> - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a
> recent OSX, it won't compile without manual fiddling).
> - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8.
> Supporting both at the same time adds a lot of overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110588#comment-15110588 ] Willem van Bergen commented on AVRO-1559: - If we're going to drop support for Ruby versions anyway, we should drop support for 1.9 as well because it is also EOL, and will no longer receive security fixes. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110581#comment-15110581 ] Martin Kleppmann commented on AVRO-1559: +1 on dropping 1.8 support but keeping 1.9 support. There's not much benefit in dropping 1.9 support at this stage, since the differences between 1.9 and 2.0 are much smaller than the differences between 1.8 and 1.9. (Ruby's version numbering was pretty messed up back then.) > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107863#comment-15107863 ] Sean Busbey commented on AVRO-1559: --- I'm +1 on dropping 1.8, provided we have a prominent release note and we're fine with the possibility of more 1.7 releases should requests come in. I'd still like to avoid expressly removing 1.9 as well. I'd prefer to build up 2.2+ support in a different gem. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107698#comment-15107698 ] Ryan Blue commented on AVRO-1559: - We just hit more problems with ruby 1.8 support in AVRO-1785. I just checked HBase and I don't think it depends on the gem after all, and Sean agreed. I think we can move forward with this. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616947#comment-14616947 ] Hudson commented on AVRO-1559: -- SUCCESS: Integrated in AvroJava #526 (See [https://builds.apache.org/job/AvroJava/526/]) Revert AVRO-1559. Drop support for Ruby 1.8. (tomwhite: rev 1689710) * /avro/trunk/BUILD.txt * /avro/trunk/CHANGES.txt * /avro/trunk/lang/ruby/lib/avro/data_file.rb * /avro/trunk/lang/ruby/lib/avro/io.rb > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616938#comment-14616938 ] ASF subversion and git services commented on AVRO-1559: --- Commit 1689710 from tomwh...@apache.org in branch 'avro/trunk' [ https://svn.apache.org/r1689710 ] Revert AVRO-1559. Drop support for Ruby 1.8. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616912#comment-14616912 ] Tom White commented on AVRO-1559: - I'll revert this until we have consensus on when Ruby 1.8 support can be dropped. Sorry for the confusion. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616874#comment-14616874 ] Sean Busbey commented on AVRO-1559: --- Just illustrative. I believe we rely on Java Avro even in our Ruby based shell, but haven't done any of the ground work to verify that. Our requiring Ruby 1.8+ also means that those who rely on extending our tooling might also be constrained in what can change about their operational environment. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616870#comment-14616870 ] Tom White commented on AVRO-1559: - [~ busbey] of course. Would you like to start it? BTW is the HBase shell using Ruby Avro, or is just an illustration that projects may find it difficult to upgrade? > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616862#comment-14616862 ] Sean Busbey commented on AVRO-1559: --- [~tomwhite] could we have a DISCUSS thread on user@avro before we move from 1.8+ to 2.0 for Ruby? > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616814#comment-14616814 ] Sean Busbey commented on AVRO-1559: --- Ruby 2.0 is bad news. Requiring it will mean that we don't work with any version of JRuby, for example, because JRuby 1.7 is Ruby 1.8 - 1.9 and JRuby 9k is Ruby 2.2. The HBase project relies on JRuby for our shell. We can probably rely on JRuby's java support to wrap the java library, but I don't if we're already doing that. We require Ruby 1.8 compatibility in our current stable line (HBase 1.y) and won't have a new major version until early 2016 probably. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616745#comment-14616745 ] Tom White commented on AVRO-1559: - OK, I just updated BUILD.txt. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616740#comment-14616740 ] Willem van Bergen commented on AVRO-1559: - No code changes necessary for that; just updating the documentation is fine. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616737#comment-14616737 ] Tom White commented on AVRO-1559: - Is that just a question of updating the version in BUILD.txt, or are there any code changes? > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616730#comment-14616730 ] Willem van Bergen commented on AVRO-1559: - Ypu may want to bump the minimum Ruby requirement to 2.0, because Ruby 1.9 is also EOL now. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616708#comment-14616708 ] Hudson commented on AVRO-1559: -- SUCCESS: Integrated in AvroJava #524 (See [https://builds.apache.org/job/AvroJava/524/]) AVRO-1559. Drop support for Ruby 1.8. Contributed by Willem van Bergen. (tomwhite: rev 1689660) * /avro/trunk/CHANGES.txt * /avro/trunk/lang/ruby/lib/avro/data_file.rb * /avro/trunk/lang/ruby/lib/avro/io.rb > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen >Assignee: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1559) Drop support for Ruby 1.8
[ https://issues.apache.org/jira/browse/AVRO-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616682#comment-14616682 ] ASF subversion and git services commented on AVRO-1559: --- Commit 1689660 from tomwh...@apache.org in branch 'avro/trunk' [ https://svn.apache.org/r1689660 ] AVRO-1559. Drop support for Ruby 1.8. Contributed by Willem van Bergen. > Drop support for Ruby 1.8 > - > > Key: AVRO-1559 > URL: https://issues.apache.org/jira/browse/AVRO-1559 > Project: Avro > Issue Type: Wish >Affects Versions: 1.7.7 >Reporter: Willem van Bergen > Fix For: 1.8.0 > > Attachments: AVRO-1559.patch > > > - Ruby 1.8 is EOL, and is even security issues aren't addressed anymore. > - It is also getting hard to set up Ruby 1.8 to run the tests (e.g. on a > recent OSX, it won't compile without manual fiddling). > - Handling character encodings in Ruby 1.9 is very different than Ruby 1.8. > Supporting both at the same time adds a lot of overhead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
