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 > >
