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
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
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
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
tjwp merged PR #2045:
URL: https://github.com/apache/avro/pull/2045
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org
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
RyanSkraba merged PR #2039:
URL: https://github.com/apache/avro/pull/2039
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
