Re: Release language modules separately

For ease of maintenance, I think we should follow these rules: - one (mono)repo - each SDK has one stable version: main/master, that's available to be released on short notice - upon release, all changed SDKs get a new, appropriate, semantic version - all current SDK versions must be compatible wit

Re: Release language modules separately

Indeed, "Commons tests" embeds avro files that aims to be used in tests for every SDKs, but we also can add meta information to minimum SDK version is required for this tests. Concretely, with this files , adding "meta.properties" on each share/test/d

Re: Release language modules separately

On Thu, Jan 12, 2023, 17:33 Christophe Le Saëc wrote: > So, if i take the latest one; i could have > lang/java 13.1 > lang/python 11.2 > lang/rust 12.3 > > So what will contains *share* folder if it should integrates some updates > between 11 & 12 and between 12 & 13 ? (some sub-folder share/11 .

Re: Release language modules separately

So, if i take the latest one; i could have lang/java 13.1 lang/python 11.2 lang/rust 12.3 So what will contains *share* folder if it should integrates some updates between 11 & 12 and between 12 & 13 ? (some sub-folder share/11 ... ? to allow lang/java to use share/13, lang/python to use share/11

Re: Release language modules separately

On Thu, Jan 12, 2023 at 3:12 PM Christophe Le Saëc wrote: > With one github repo; how to manage share > folder ? i mean if one > version need updates on this repo but not the older. > > As an example, this JIRA AVRO-3591 >

Re: Release language modules separately

With one github repo; how to manage share folder ? i mean if one version need updates on this repo but not the older. As an example, this JIRA AVRO-3591 aims to create commons inter sdk unit tests

Re: Release language modules separately

On Wed, Jan 11, 2023 at 9:27 PM Ryan Skraba wrote: > Hey -- how does this sound for rolling out this strategy. > > 1) No changes to 1.11 branch. We can release 1.11.2 to bring some of > the immediate bug and security fixes. > > 2) The next major release of Avro will be 12.0.0 for the specificati

Re: Release language modules separately

Hey -- how does this sound for rolling out this strategy. 1) No changes to 1.11 branch. We can release 1.11.2 to bring some of the immediate bug and security fixes. 2) The next major release of Avro will be 12.0.0 for the specification and all SDK (except maybe Rust) and we'll start following se

Re: Release language modules separately

+1 for separating out the releasesе too On Sat, Jan 7, 2023 at 4:46 AM Ryan Blue wrote: > +1 for separating out the releases and starting a vote on just that. We can > debate the other details as we go. > > On Thu, Jan 5, 2023 at 12:25 PM Tim Perkins wrote: > > > On Wed, Jan 4, 2023 at 1:15 PM

Re: Release language modules separately

+1 for separating out the releases and starting a vote on just that. We can debate the other details as we go. On Thu, Jan 5, 2023 at 12:25 PM Tim Perkins wrote: > On Wed, Jan 4, 2023 at 1:15 PM Ryan Skraba wrote: > > > Maybe a good way to get to consensus would be to list the possible > > acti

Re: Release language modules separately

On Wed, Jan 4, 2023 at 1:15 PM Ryan Skraba wrote: > Maybe a good way to get to consensus would be to list the possible > actions we could take, and prioritize them? > One of the actions that I would like to see is the compilation of which parts of the spec each language implements. This would be

Re: Release language modules separately

👍 Le jeu. 5 janv. 2023 à 13:58, Martin Grigorov a écrit : > Hi, > > On Thu, Jan 5, 2023 at 2:40 PM Christophe Le Saëc > wrote: > > > I'm also in favor of this idea (+1). > > Just to figure out,*splitting the language SDKs to separate releases and > > releasing separately.* : Concretely, is this

Re: Release language modules separately

Hi, On Thu, Jan 5, 2023 at 2:40 PM Christophe Le Saëc wrote: > I'm also in favor of this idea (+1). > Just to figure out,*splitting the language SDKs to separate releases and > releasing separately.* : Concretely, is this means that there will be one > github repo for each language (So 10 avro g

Re: Release language modules separately

I'm also in favor of this idea (+1). Just to figure out,*splitting the language SDKs to separate releases and releasing separately.* : Concretely, is this means that there will be one github repo for each language (So 10 avro github repo); or is there any other "github" trick to manage separate rel

Re: Release language modules separately

Thanks, Ryan! I have forgotten about the previous discussion! On Wed, Jan 4, 2023 at 8:15 PM Ryan Skraba wrote: > Hello! We've started and stopped this discussion a couple of times -- > but it ends up getting a bit bogged down in details, and there's so > much going on that we end on sticking

Re: Release language modules separately

Hello! We've started and stopped this discussion a couple of times -- but it ends up getting a bit bogged down in details, and there's so much going on that we end on sticking with the status quo! I would love to have this discussion again though and come to a conclusion. We could be doing quite

Re: Release language modules separately

On Wed, 4 Jan 2023 at 08:15, Martin Grigorov wrote: > [...] the problem is the availability of active maintainers. This is another issue, and important too IMHO. I'm just not certain there's a solution though. I'll raise another thread if I ever have ideas to tackle it. Kind regards, Oscar --

Re: Release language modules separately

Hi Oscar, On Wed, Jan 4, 2023 at 9:01 AM Oscar Westra van Holthe - Kind < os...@westravanholthe.nl> 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

Re: Release language modules separately

Hello Khrystyna, On Wed, Jan 4, 2023 at 2:31 AM Khrystyna Popadyuk < khrystyna.popad...@gmail.com> wrote: > Hi Martin, > > Happy new year too! > > I think a split release for modules/languages is a great idea. > > As we are going to have different versions for different languages, is > there a se

Re: Release language modules separately

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 w

Re: Release language modules separately

Hi Martin, Happy new year too! I think a split release for modules/languages is a great idea. As we are going to have different versions for different languages, is there a sense to continue linking package version to specification version? You mentioned that modules that have version 1.*.* do n

Release language modules separately

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 rathe