Great, thanks for the advice - maybe I'll start by creating a local build which is 1.8.2 plus the AVRO-1723 fix and, if that seems to go well, lobbying in dev@ for 1.8.2.1.
On Tue, Dec 4, 2018 at 9:18 AM Sean Busbey <[email protected]> wrote: > Hi David! > > The fastest way to get a release with AVRO-1723 in it is to subscribe > to the dev@avro list and help push forward on getting a release out. > we can discussion options for it on dev@avro. For example, if there > are too many blockers waiting around for 1.8.3 it might make sense to > get a 1.8.2.1 out. > On Fri, Nov 30, 2018 at 5:28 PM David Carlton <[email protected]> > wrote: > > > > I'm running into https://issues.apache.org/jira/browse/AVRO-1723 > (forward declarations in Avro IDL), and I'm wondering what the timing is > for a release that contains that fix? I see > https://issues.apache.org/jira/browse/AVRO-2163 for releasing 1.8.3, but > it's not clear from that Jira what the timeline is for 1.8.3 and whether it > will contain a fix for AVRO-1723. So I'm trying to figure out if I should > generate my own local build of Avro containing the patch for AVRO-1723, or > if I should just write that protocol in JSON instead of IDL and then switch > it over to IDL once 1.8.3 is released. > > > > Thanks for any advice you have, > > David Carlton > > [email protected] > > > > -- > busbey > -- David Carlton [email protected]
