Hi, Is there an upcoming 1.7 fix release that can pick this up?
I'm asking so I could know if I can wait for a 1.7 fix release or move my company's codebase to a forked 1.7 On Tue, Oct 4, 2016 at 4:02 PM, radai <[email protected]> wrote: > Thanks, > > I've opened a PR to backport to 1.8 (https://github.com/apache/ > avro/pull/140 - has everything that landed originally except additions to > CHANGES.txt) > > For 1.7, I had to 1st bring the branch to compile (PR here - > https://github.com/apache/avro/pull/139) and will backport in a > subsequent PR. > > > On Tue, Oct 4, 2016 at 6:28 AM, Sean Busbey <[email protected]> wrote: > >> (For others, the jira under discussion is AVRO-1901 >> https://issues.apache.org/jira/browse/AVRO-1901) >> >> On Tue, Oct 4, 2016 at 8:28 AM, Sean Busbey <[email protected]> wrote: >> > yes, it looks like the jira landed in 1.9, though there isn't a fix >> > version set. I don't see anything in the patch that would prevent a >> > backport to 1.7. >> > >> > On Mon, Oct 3, 2016 at 2:28 PM, radai <[email protected]> >> wrote: >> >> Hi, >> >> >> >> I've recently encountered a bug in avro code generation, for which I >> >> submitted a fix ( >> >> https://github.com/apache/avro/commit/be33922c03bd229b885fb9 >> d664b55ce308f6ffaf >> >> ). >> >> >> >> The issue was discovered while trying to migrate a sizable codebase >> from >> >> avro 1.4 to 1.7 >> >> >> >> Would it be possible to back-port this fix to 1.7? bumping 1.7 to >> latest >> >> would be a lot easier than trying to upgrade 1.4 and now 1.7 code to >> 1.9 >> >> (which is where this will will end up in, when its released?) >> >> >> >> I can just open a PR porting the fix to the 1.7 branch (maybe 1.8 >> branch as >> >> well, for consistency), if thats the procedure. >> >> >> >> Thanks in advance, >> >> >> >> >> >> Radai. >> > >> > >> > >> > -- >> > busbey >> >> >> >> -- >> busbey >> > >
