Hi Folks! The appropriate place to discuss what gets merged and timing of not-yet-done releases is the dev@avro list. There's even been a brief discussion already about the tradeoff between trying to squeeze more things in to the next 1.8.z release vs working on getting a regular release cadence.
I don't mean to indicate that these discussions aren't important; I'd love to see them continue on the dev list. On Thu, Apr 20, 2017 at 10:20 AM, Gill, John <[email protected]> wrote: > Suraj, > > Is there any way that we could look at picking up PR 217 which fixes > AVRO-766 & AVRO-1167? These are long outstanding memory leak issues in the C > implementation. > > > > -- John > > > > > > From: Suraj Acharya <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Thursday, April 20, 2017 at 7:44 AM > To: "[email protected]" <[email protected]> > Subject: Re: When is v1.8.2 going to be released? > > > > Hi Javier, > > > > I made the last two tags so i can give you some context. > > The RC2 and RC3 failed for license issues in java and versioning in JS. > > I have fixed both of those. However, in the days after I started a couple of > people wanted a few code pieces merged. I had stopped that since I was > working on a release and that would cause continuous churn. I am giving > people time to merge any code in before I start back. > > I intend to make another release in the next few days. I can say I will try > to make sure it is not paused. > > > > Regarding when will this be released. I can't give you a definite date. I > try to make an hour or so a day for open source work and sometimes I am not > able to do the same. Also, it needs community help to pass an RC too. All I > can say is soon. > > > > Hope that helps. > > > > S > > > > On Thu, Apr 20, 2017 at 4:50 AM, Javier Holguera <[email protected]> > wrote: > > Hi, > > > > My company is really looking forward to using some of the bug fixes that > will come with this version. We are even considering compiling and uploading > Avro 1.8.2 into our own Artifactory. > > > > Obviously it would be much better if we could just pull from public Maven > repos, as usual. > > > > When are you planning to release this version? The Github tags suggest there > was an attempt months ago and a few more two weeks ago. > > > > Is this really imminent or are there chances that it will be paused like it > happened in November? > > > > Thanks. > > > > Javier. > > -- busbey
