Hello Martin, Thank you and I hope the release is around the corner also. I'm on another Apache project and we follow the same process (3+ binding votes for a release). To my knowledge, there isn't a well defined process for number of release candidates or duration between RCs and a final release, so was curious based on previous releases if Avro PMCs could provide a ballpark from RC1 to final release.
I *very* much appreciate fielding questions from random folks in the community. :) Cheers, Eric On Tue, Jul 26, 2022 at 7:36 AM Martin Grigorov <[email protected]> wrote: > Hi Eric, > > As you might know Apache releases are being voted for at least 3 days and > need 3 binding votes (i.e. from PMC members). So it depends on the start > date. > From the other thread I have the feeling that Ryan will do it these days! > But I had the same feeling few months ago too :-) > > Martin > > On Tue, Jul 26, 2022 at 5:12 PM Eric Johnson <[email protected]> wrote: > > > Hello Ismael and Martin, > > > > A related question on the next release, assuming an RC1 is forthcoming, > is > > there a rough estimate when the final release would be available? Is > there > > any chance the final release would be available by 15-Aug? > > > > Context is that we're using the Avro library and are planning our > upcoming > > releases and I'd like to pick up the next Avro release. I'm interested in > > including Nilesh's contribution as well as > > https://github.com/apache/avro/pull/1640 which addresses a known CVE. > > > > Respectfully, Eric > > > > On Tue, Jul 26, 2022 at 6:32 AM Ismaël Mejía <[email protected]> wrote: > > > > > Hello Nilesh, > > > > > > The Avro project makes around 2-3 releases per year since 2019 (when > > > we got a new release pace). Next release will be 1.11.1 (the link > > > Martin referred), it should be happening hopefully soon, your > > > contribution will be part of it. > > > > > > We tend to cherry-pick as much as we can so patch releases (1.11.1, > > > 1.11.2, etc) tend to be beefier. Also Avro DOES NOT follow semantic > > > versioning but we tend to be pretty conservative on not breaking > > > backwards compatibility without strong reasons and without giving a > > > good time frame to adapt. > > > > > > After writing this I realize that we should probably include a section > > > about releases and compatibility in the new website. I filled > > > https://issues.apache.org/jira/browse/AVRO-3588 to add it once we have > > > the new website out. > > > > > > Regards, > > > Ismael > > > > > > Extra: Slightly unrelated, but I noticed your email affiliation and > > > somehow it made me think that I have wanted for years to use Google's > > > OSS-Fuzz to strength Avro's C/C++ (and now) Rust implementations. I > > > filled https://issues.apache.org/jira/browse/AVRO-3128 long time ago, > > > in case you or someone else wants to give it a try. > > > > > > On Tue, Jul 26, 2022 at 9:10 AM Martin Grigorov <[email protected]> > > > wrote: > > > > > > > > https://lists.apache.org/thread/w5kv5h774zx825o2yj285wwznx1sodn8 > > > > > > > > On Tue, Jul 26, 2022 at 3:16 AM Nilesh Yadav > > <[email protected] > > > > > > > > wrote: > > > > > > > > > Hello, > > > > > > > > > > I've recently contributed to Avro C++ library with > > > > > https://github.com/apache/avro/pull/1736 > > > > > > > > > > I would like to understand the release cycle of Avro library > changes. > > > What > > > > > are the steps involved? > > > > > Approximately when this feature would be available in public > library? > > > > > > > > > > Thank you, > > > > > Nilesh > > > > > > > > > > >
