Hi Oscar, On Wed, Jan 4, 2023 at 9:01 AM Oscar Westra van Holthe - Kind < [email protected]> wrote:
> Happy new year! > > While the frustration of a slow release cadence is something I feel as > well, splitting the release will not help there. It really boils down to > how often we want to do a release, and specifically how fast we can merge > PRs (safely). If we cannot speed that up, releasing more often won't help. > Here the problem is the availability of active maintainers. My idea is that tThe lack of help for reviewing and merging PRs for lang X should not stop the activity in lang Y, i.e. lang Y should be able to make new releases. > > Having said that, it's a good idea to split releases anyway. It makes no > sense to release a module that hasn't changed, or give a module a large > version increase if it only has updated dependencies. > > I do agree with the implied proposal to keep the current semantic > versioning scheme: spec.major.minor, where the spec version denotes > compatibility of the binary format and parsing canonical form. That makes > it possible to at least have some idea about interoperability without > consulting a lookup table. > > Kind regards, > Oscar > > -- > Oscar Westra van Holthe - Kind <[email protected]> > > Op di 3 jan. 2023 15:01 schreef Martin Grigorov <[email protected]>: > > > Happy new year Avro community! > > I wish you to have a lot of fun while developing your projects! > > > > I'd like to propose to make it possible to release a single module/lang. > > At the moment all modules share the same version and are being released > > together. > > The problem is that the release cadence is rather slow and some users > > complain about it, e.g. the C# and Rust ones. > > > > The only "problem" I see is that the modules will have different versions > > from now on, e.g. Java will be 1.11.1 and the C# module will be 1.12.0. > > (The Rust one is still at 0.15.0 :-) ). > > This might confuse some users but we just have to make it clear in the > docs > > that the important number is the Avro spec version, i.e. "1". The modules > > do not implement the whole set of features > > even now. > > > > As of now, a release of a single module (or a sub-set of modules) will > > require the same ASF release rules (3 binding +1s, at least 72 hours for > > voting, etc.). > > > > What do you think ? > > > > Regards, > > Martin > > >
