You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by Ryan Skraba <ry...@skraba.com> on 2021/02/23 14:44:14 UTC
[PROPOSAL] Let's prepare a 1.10.2
Hello Avro community,
We've kept up a decent cadence over the last few releases of every six
months! At this rate, the next release would be in May for 1.11.0 (and
we're looking forward to it -- seeya python2!)
In the meantime, I was thinking it would be good to release another 1.10.2,
specifically to help bump some downstream projects (see
https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a bugfix
release instead of 1.11.x for a couple of reasons: it would be ideal to get
this out sooner rather than later, we're already seeing some interest and
effort for bumping Avro, and it's reassuring for other projects to see
bugfix releases.
In my opinion, with experience it's getting easier to do these minor
releases. I'd happily volunteer to shepherd this one through, and (as
always) if anyone wants to shadow the process we can do it together.
What do you think? Are there any other bugfixes that you'd like to see in
a 1.10.x release?[1]
Best regards, Ryan
[1]
https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
Re: [PROPOSAL] Let's prepare a 1.10.2
Posted by Ryan Skraba <ry...@skraba.com>.
Thanks! I've cherry-picked the commit for AVRO-3023 for Ruby 3
compatibility, but just omitted the Github Actions part -- there was a one
line fix to get the travis-ci running again (although it's still pretty
flakey)
For the moment, ruby:2 is tested by Travis, and I tested ruby:3 manually
on the branch using:
docker run -t --volume $(pwd):/opt/workdir --workdir /opt/workdir ruby:3
bash -c "apt update && apt install -y libsnappy-dev && cd lang/ruby &&
./build.sh test"
I'm preparing release candidate artifacts, but I've committed the branch
and pushed the tag for RC1. Somebody is going to have to teach me how to
temporarily disable JIRA notifications to the mailing list during this
proces -- my apolologies for the volume!
All my best! Ryan
On Thu, Mar 4, 2021 at 7:52 PM Tim Perkins <tj...@gmail.com> wrote:
> Hi Ryan,
>
> Thank you for your work so far on the 1.10.2!
>
> I'd suggest that we backport the following to ensure compatibility the
> latest Ruby release:
>
> AVRO-3023: Test against Ruby 3.0 (#1048)
>
>
> But that likely depends on backporting:
>
> AVRO-3009 Test in GitHub Actions (#1043)
>
> Which might be a much larger task to take on, but it has been a great
> improvement for testing in general.
>
> Thanks!
>
> -Tim
>
>
> On Wed, Mar 3, 2021 at 5:08 AM Ryan Skraba <ry...@skraba.com> wrote:
>
> > Hello! I've done a bunch of cherry-picks from master -- I tried to catch
> > all of the bug fixes and performance improvements. I was pretty
> aggressive
> > about bumping dependencies, including all patch and minor version
> changes.
> >
> > You can see the commits that I propose to cherry-pick at
> > https://github.com/apache/avro/pull/1117 (I'm using a draft PR, but go
> > ahead and smash that approve button if you like it).
> >
> > Here's a list of the commits on master that were NOT cherry-picked. Let
> me
> > know if you think one or more should be applied!
> >
> > AVRO-2975: Enable PHP linting and fix its errors (#984)
> > AVRO-9262: Configure dependency updates via dependabot
> > Bump hadoop-client from 3.2.1 to 3.3.0 in /lang/java
> > Bump maven.version from 3.3.9 to 3.6.3 in /lang/java
> > AVRO-2994: Maven 3.6.3 from Apache servers. (#1028)
> > AVRO-3009 Test in GitHub Actions (#1043)
> > AVRO-3009: Update Status Badges in Readme
> > AVRO-3023: Test against Ruby 3.0 (#1048)
> > AVRO-3030: Remove the PUBLIC_DEPRECATED (#1069)
> > AVRO-3033: Fix flaky file descriptor test (#1078)
> > Modernizing Zigzag (#1104)
> > Ignore jetty >= 10 dependency upgrades from dependabot (JDK 11 required)
> >
> > Some of the questions I faced:
> >
> > 1) I included the jackson bump to 2.12.x: is this going to be a problem
> and
> > should it wait for 1.11.0?
> > 2) I excluded the maven bump to 3.6.3: if I remember correctly this
> breaks
> > the avro-maven-plugin for developers using older versions of maven.
> >
> > Here's the list of AVRO issues with the 1.10.2 Fix Version -- Some of
> them
> > look like they should be Resolved, since they've been committed to
> master.
> >
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
> >
> > There's a log of open PRs, I'm scanning through to see if any are bug
> fixes
> > that could be applied sooner rather than later!
> >
> > I'd love to build a release candidate before the weekend, all feedback
> > welcome!
> >
> > All my best, Ryan
> >
> > On Sun, Feb 28, 2021 at 12:34 PM Ismaël Mejía <ie...@gmail.com> wrote:
> >
> > > BIg +1 Ryan,
> > > It definitely makes sense to have this release and is consistent with
> > > what we have been doing in the last versions.
> > >
> > > We should ideally also catch some dependency upgrades for the
> > > javascript implementation if there is anyone with the expertise who
> > > wants to contribute to this it will be great.
> > >
> > >
> > > On Tue, Feb 23, 2021 at 3:57 PM Tim Perkins <tj...@gmail.com>
> > wrote:
> > > >
> > > > There have been some recent Ruby performance fixes that would be good
> > to
> > > > include in a 1.10.x.
> > > >
> > > > On Tue, Feb 23, 2021 at 9:44 AM Ryan Skraba <ry...@skraba.com> wrote:
> > > >
> > > > > Hello Avro community,
> > > > >
> > > > > We've kept up a decent cadence over the last few releases of every
> > six
> > > > > months! At this rate, the next release would be in May for 1.11.0
> > (and
> > > > > we're looking forward to it -- seeya python2!)
> > > > >
> > > > > In the meantime, I was thinking it would be good to release another
> > > 1.10.2,
> > > > > specifically to help bump some downstream projects (see
> > > > > https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a
> > > bugfix
> > > > > release instead of 1.11.x for a couple of reasons: it would be
> ideal
> > > to get
> > > > > this out sooner rather than later, we're already seeing some
> interest
> > > and
> > > > > effort for bumping Avro, and it's reassuring for other projects to
> > see
> > > > > bugfix releases.
> > > > >
> > > > > In my opinion, with experience it's getting easier to do these
> minor
> > > > > releases. I'd happily volunteer to shepherd this one through, and
> > (as
> > > > > always) if anyone wants to shadow the process we can do it
> together.
> > > > >
> > > > > What do you think? Are there any other bugfixes that you'd like to
> > > see in
> > > > > a 1.10.x release?[1]
> > > > >
> > > > > Best regards, Ryan
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
> > > > >
> > >
> >
>
Re: [PROPOSAL] Let's prepare a 1.10.2
Posted by Tim Perkins <tj...@gmail.com>.
Hi Ryan,
Thank you for your work so far on the 1.10.2!
I'd suggest that we backport the following to ensure compatibility the
latest Ruby release:
AVRO-3023: Test against Ruby 3.0 (#1048)
But that likely depends on backporting:
AVRO-3009 Test in GitHub Actions (#1043)
Which might be a much larger task to take on, but it has been a great
improvement for testing in general.
Thanks!
-Tim
On Wed, Mar 3, 2021 at 5:08 AM Ryan Skraba <ry...@skraba.com> wrote:
> Hello! I've done a bunch of cherry-picks from master -- I tried to catch
> all of the bug fixes and performance improvements. I was pretty aggressive
> about bumping dependencies, including all patch and minor version changes.
>
> You can see the commits that I propose to cherry-pick at
> https://github.com/apache/avro/pull/1117 (I'm using a draft PR, but go
> ahead and smash that approve button if you like it).
>
> Here's a list of the commits on master that were NOT cherry-picked. Let me
> know if you think one or more should be applied!
>
> AVRO-2975: Enable PHP linting and fix its errors (#984)
> AVRO-9262: Configure dependency updates via dependabot
> Bump hadoop-client from 3.2.1 to 3.3.0 in /lang/java
> Bump maven.version from 3.3.9 to 3.6.3 in /lang/java
> AVRO-2994: Maven 3.6.3 from Apache servers. (#1028)
> AVRO-3009 Test in GitHub Actions (#1043)
> AVRO-3009: Update Status Badges in Readme
> AVRO-3023: Test against Ruby 3.0 (#1048)
> AVRO-3030: Remove the PUBLIC_DEPRECATED (#1069)
> AVRO-3033: Fix flaky file descriptor test (#1078)
> Modernizing Zigzag (#1104)
> Ignore jetty >= 10 dependency upgrades from dependabot (JDK 11 required)
>
> Some of the questions I faced:
>
> 1) I included the jackson bump to 2.12.x: is this going to be a problem and
> should it wait for 1.11.0?
> 2) I excluded the maven bump to 3.6.3: if I remember correctly this breaks
> the avro-maven-plugin for developers using older versions of maven.
>
> Here's the list of AVRO issues with the 1.10.2 Fix Version -- Some of them
> look like they should be Resolved, since they've been committed to master.
>
>
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
>
> There's a log of open PRs, I'm scanning through to see if any are bug fixes
> that could be applied sooner rather than later!
>
> I'd love to build a release candidate before the weekend, all feedback
> welcome!
>
> All my best, Ryan
>
> On Sun, Feb 28, 2021 at 12:34 PM Ismaël Mejía <ie...@gmail.com> wrote:
>
> > BIg +1 Ryan,
> > It definitely makes sense to have this release and is consistent with
> > what we have been doing in the last versions.
> >
> > We should ideally also catch some dependency upgrades for the
> > javascript implementation if there is anyone with the expertise who
> > wants to contribute to this it will be great.
> >
> >
> > On Tue, Feb 23, 2021 at 3:57 PM Tim Perkins <tj...@gmail.com>
> wrote:
> > >
> > > There have been some recent Ruby performance fixes that would be good
> to
> > > include in a 1.10.x.
> > >
> > > On Tue, Feb 23, 2021 at 9:44 AM Ryan Skraba <ry...@skraba.com> wrote:
> > >
> > > > Hello Avro community,
> > > >
> > > > We've kept up a decent cadence over the last few releases of every
> six
> > > > months! At this rate, the next release would be in May for 1.11.0
> (and
> > > > we're looking forward to it -- seeya python2!)
> > > >
> > > > In the meantime, I was thinking it would be good to release another
> > 1.10.2,
> > > > specifically to help bump some downstream projects (see
> > > > https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a
> > bugfix
> > > > release instead of 1.11.x for a couple of reasons: it would be ideal
> > to get
> > > > this out sooner rather than later, we're already seeing some interest
> > and
> > > > effort for bumping Avro, and it's reassuring for other projects to
> see
> > > > bugfix releases.
> > > >
> > > > In my opinion, with experience it's getting easier to do these minor
> > > > releases. I'd happily volunteer to shepherd this one through, and
> (as
> > > > always) if anyone wants to shadow the process we can do it together.
> > > >
> > > > What do you think? Are there any other bugfixes that you'd like to
> > see in
> > > > a 1.10.x release?[1]
> > > >
> > > > Best regards, Ryan
> > > >
> > > > [1]
> > > >
> > > >
> >
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
> > > >
> >
>
Re: [PROPOSAL] Let's prepare a 1.10.2
Posted by Ryan Skraba <ry...@skraba.com>.
Hello! Yes, that really should be a goal, and migrating from 1.10.1 to
1.10.2 should be transparent for Java users -- with some obvious caveats
(such as if you were relying on buggy behaviour in your code, and that bug
was fixed).
I've only checked the avro-1.10.2-SNAPSHOT.jar so far, but it's at 100%
compatible:
Test Results
Total Java Modules 1
Total Methods / Classes 1624 / 239
Compatibility 100%
For info, I use the following docker command to generate the compatibility
report (after doing a mvn install):
mkdir -p /tmp/japi && chmod -R 777 /tmp/japi
docker run -it --rm -v /home/rskraba/.m2:/opt/m2:ro -v
/tmp/japi:/compat_reports \
joschi/japi-compliance-checker:2.4-1 \
/opt/m2/repository/org/apache/avro/avro/1.10.1/avro-1.10.1.jar \
/opt/m2/repository/org/apache/avro/avro/1.10.2-SNAPSHOT/avro-1.10.2-SNAPSHOT.jar
If we've broken anything unreasonably, please bring it up! All my best, Ryan
On Wed, Mar 3, 2021 at 5:38 PM Michael Heuer <he...@gmail.com> wrote:
> Hello Ryan,
>
> To clarify, since Avro doesn't strictly follow the semantic versioning
> standard, is it the intention that 1.10.2 be binary compatible with 1.10.1
> for lang/java?
>
> Thank you,
>
> michael
>
>
> > On Mar 3, 2021, at 4:08 AM, Ryan Skraba <ry...@skraba.com> wrote:
> >
> > Hello! I've done a bunch of cherry-picks from master -- I tried to catch
> > all of the bug fixes and performance improvements. I was pretty
> aggressive
> > about bumping dependencies, including all patch and minor version
> changes.
> >
> > You can see the commits that I propose to cherry-pick at
> > https://github.com/apache/avro/pull/1117 (I'm using a draft PR, but go
> > ahead and smash that approve button if you like it).
> >
> > Here's a list of the commits on master that were NOT cherry-picked. Let
> me
> > know if you think one or more should be applied!
> >
> > AVRO-2975: Enable PHP linting and fix its errors (#984)
> > AVRO-9262: Configure dependency updates via dependabot
> > Bump hadoop-client from 3.2.1 to 3.3.0 in /lang/java
> > Bump maven.version from 3.3.9 to 3.6.3 in /lang/java
> > AVRO-2994: Maven 3.6.3 from Apache servers. (#1028)
> > AVRO-3009 Test in GitHub Actions (#1043)
> > AVRO-3009: Update Status Badges in Readme
> > AVRO-3023: Test against Ruby 3.0 (#1048)
> > AVRO-3030: Remove the PUBLIC_DEPRECATED (#1069)
> > AVRO-3033: Fix flaky file descriptor test (#1078)
> > Modernizing Zigzag (#1104)
> > Ignore jetty >= 10 dependency upgrades from dependabot (JDK 11 required)
> >
> > Some of the questions I faced:
> >
> > 1) I included the jackson bump to 2.12.x: is this going to be a problem
> and
> > should it wait for 1.11.0?
> > 2) I excluded the maven bump to 3.6.3: if I remember correctly this
> breaks
> > the avro-maven-plugin for developers using older versions of maven.
> >
> > Here's the list of AVRO issues with the 1.10.2 Fix Version -- Some of
> them
> > look like they should be Resolved, since they've been committed to
> master.
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
> >
> > There's a log of open PRs, I'm scanning through to see if any are bug
> fixes
> > that could be applied sooner rather than later!
> >
> > I'd love to build a release candidate before the weekend, all feedback
> > welcome!
> >
> > All my best, Ryan
> >
> > On Sun, Feb 28, 2021 at 12:34 PM Ismaël Mejía <ie...@gmail.com> wrote:
> >
> >> BIg +1 Ryan,
> >> It definitely makes sense to have this release and is consistent with
> >> what we have been doing in the last versions.
> >>
> >> We should ideally also catch some dependency upgrades for the
> >> javascript implementation if there is anyone with the expertise who
> >> wants to contribute to this it will be great.
> >>
> >>
> >> On Tue, Feb 23, 2021 at 3:57 PM Tim Perkins <tj...@gmail.com>
> wrote:
> >>>
> >>> There have been some recent Ruby performance fixes that would be good
> to
> >>> include in a 1.10.x.
> >>>
> >>> On Tue, Feb 23, 2021 at 9:44 AM Ryan Skraba <ry...@skraba.com> wrote:
> >>>
> >>>> Hello Avro community,
> >>>>
> >>>> We've kept up a decent cadence over the last few releases of every six
> >>>> months! At this rate, the next release would be in May for 1.11.0
> (and
> >>>> we're looking forward to it -- seeya python2!)
> >>>>
> >>>> In the meantime, I was thinking it would be good to release another
> >> 1.10.2,
> >>>> specifically to help bump some downstream projects (see
> >>>> https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a
> >> bugfix
> >>>> release instead of 1.11.x for a couple of reasons: it would be ideal
> >> to get
> >>>> this out sooner rather than later, we're already seeing some interest
> >> and
> >>>> effort for bumping Avro, and it's reassuring for other projects to see
> >>>> bugfix releases.
> >>>>
> >>>> In my opinion, with experience it's getting easier to do these minor
> >>>> releases. I'd happily volunteer to shepherd this one through, and (as
> >>>> always) if anyone wants to shadow the process we can do it together.
> >>>>
> >>>> What do you think? Are there any other bugfixes that you'd like to
> >> see in
> >>>> a 1.10.x release?[1]
> >>>>
> >>>> Best regards, Ryan
> >>>>
> >>>> [1]
> >>>>
> >>>>
> >>
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
> >>>>
> >>
>
>
Re: [PROPOSAL] Let's prepare a 1.10.2
Posted by Michael Heuer <he...@gmail.com>.
Hello Ryan,
To clarify, since Avro doesn't strictly follow the semantic versioning standard, is it the intention that 1.10.2 be binary compatible with 1.10.1 for lang/java?
Thank you,
michael
> On Mar 3, 2021, at 4:08 AM, Ryan Skraba <ry...@skraba.com> wrote:
>
> Hello! I've done a bunch of cherry-picks from master -- I tried to catch
> all of the bug fixes and performance improvements. I was pretty aggressive
> about bumping dependencies, including all patch and minor version changes.
>
> You can see the commits that I propose to cherry-pick at
> https://github.com/apache/avro/pull/1117 (I'm using a draft PR, but go
> ahead and smash that approve button if you like it).
>
> Here's a list of the commits on master that were NOT cherry-picked. Let me
> know if you think one or more should be applied!
>
> AVRO-2975: Enable PHP linting and fix its errors (#984)
> AVRO-9262: Configure dependency updates via dependabot
> Bump hadoop-client from 3.2.1 to 3.3.0 in /lang/java
> Bump maven.version from 3.3.9 to 3.6.3 in /lang/java
> AVRO-2994: Maven 3.6.3 from Apache servers. (#1028)
> AVRO-3009 Test in GitHub Actions (#1043)
> AVRO-3009: Update Status Badges in Readme
> AVRO-3023: Test against Ruby 3.0 (#1048)
> AVRO-3030: Remove the PUBLIC_DEPRECATED (#1069)
> AVRO-3033: Fix flaky file descriptor test (#1078)
> Modernizing Zigzag (#1104)
> Ignore jetty >= 10 dependency upgrades from dependabot (JDK 11 required)
>
> Some of the questions I faced:
>
> 1) I included the jackson bump to 2.12.x: is this going to be a problem and
> should it wait for 1.11.0?
> 2) I excluded the maven bump to 3.6.3: if I remember correctly this breaks
> the avro-maven-plugin for developers using older versions of maven.
>
> Here's the list of AVRO issues with the 1.10.2 Fix Version -- Some of them
> look like they should be Resolved, since they've been committed to master.
>
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
>
> There's a log of open PRs, I'm scanning through to see if any are bug fixes
> that could be applied sooner rather than later!
>
> I'd love to build a release candidate before the weekend, all feedback
> welcome!
>
> All my best, Ryan
>
> On Sun, Feb 28, 2021 at 12:34 PM Ismaël Mejía <ie...@gmail.com> wrote:
>
>> BIg +1 Ryan,
>> It definitely makes sense to have this release and is consistent with
>> what we have been doing in the last versions.
>>
>> We should ideally also catch some dependency upgrades for the
>> javascript implementation if there is anyone with the expertise who
>> wants to contribute to this it will be great.
>>
>>
>> On Tue, Feb 23, 2021 at 3:57 PM Tim Perkins <tj...@gmail.com> wrote:
>>>
>>> There have been some recent Ruby performance fixes that would be good to
>>> include in a 1.10.x.
>>>
>>> On Tue, Feb 23, 2021 at 9:44 AM Ryan Skraba <ry...@skraba.com> wrote:
>>>
>>>> Hello Avro community,
>>>>
>>>> We've kept up a decent cadence over the last few releases of every six
>>>> months! At this rate, the next release would be in May for 1.11.0 (and
>>>> we're looking forward to it -- seeya python2!)
>>>>
>>>> In the meantime, I was thinking it would be good to release another
>> 1.10.2,
>>>> specifically to help bump some downstream projects (see
>>>> https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a
>> bugfix
>>>> release instead of 1.11.x for a couple of reasons: it would be ideal
>> to get
>>>> this out sooner rather than later, we're already seeing some interest
>> and
>>>> effort for bumping Avro, and it's reassuring for other projects to see
>>>> bugfix releases.
>>>>
>>>> In my opinion, with experience it's getting easier to do these minor
>>>> releases. I'd happily volunteer to shepherd this one through, and (as
>>>> always) if anyone wants to shadow the process we can do it together.
>>>>
>>>> What do you think? Are there any other bugfixes that you'd like to
>> see in
>>>> a 1.10.x release?[1]
>>>>
>>>> Best regards, Ryan
>>>>
>>>> [1]
>>>>
>>>>
>> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
>>>>
>>
Re: [PROPOSAL] Let's prepare a 1.10.2
Posted by Ryan Skraba <ry...@skraba.com>.
Hello! I've done a bunch of cherry-picks from master -- I tried to catch
all of the bug fixes and performance improvements. I was pretty aggressive
about bumping dependencies, including all patch and minor version changes.
You can see the commits that I propose to cherry-pick at
https://github.com/apache/avro/pull/1117 (I'm using a draft PR, but go
ahead and smash that approve button if you like it).
Here's a list of the commits on master that were NOT cherry-picked. Let me
know if you think one or more should be applied!
AVRO-2975: Enable PHP linting and fix its errors (#984)
AVRO-9262: Configure dependency updates via dependabot
Bump hadoop-client from 3.2.1 to 3.3.0 in /lang/java
Bump maven.version from 3.3.9 to 3.6.3 in /lang/java
AVRO-2994: Maven 3.6.3 from Apache servers. (#1028)
AVRO-3009 Test in GitHub Actions (#1043)
AVRO-3009: Update Status Badges in Readme
AVRO-3023: Test against Ruby 3.0 (#1048)
AVRO-3030: Remove the PUBLIC_DEPRECATED (#1069)
AVRO-3033: Fix flaky file descriptor test (#1078)
Modernizing Zigzag (#1104)
Ignore jetty >= 10 dependency upgrades from dependabot (JDK 11 required)
Some of the questions I faced:
1) I included the jackson bump to 2.12.x: is this going to be a problem and
should it wait for 1.11.0?
2) I excluded the maven bump to 3.6.3: if I remember correctly this breaks
the avro-maven-plugin for developers using older versions of maven.
Here's the list of AVRO issues with the 1.10.2 Fix Version -- Some of them
look like they should be Resolved, since they've been committed to master.
https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
There's a log of open PRs, I'm scanning through to see if any are bug fixes
that could be applied sooner rather than later!
I'd love to build a release candidate before the weekend, all feedback
welcome!
All my best, Ryan
On Sun, Feb 28, 2021 at 12:34 PM Ismaël Mejía <ie...@gmail.com> wrote:
> BIg +1 Ryan,
> It definitely makes sense to have this release and is consistent with
> what we have been doing in the last versions.
>
> We should ideally also catch some dependency upgrades for the
> javascript implementation if there is anyone with the expertise who
> wants to contribute to this it will be great.
>
>
> On Tue, Feb 23, 2021 at 3:57 PM Tim Perkins <tj...@gmail.com> wrote:
> >
> > There have been some recent Ruby performance fixes that would be good to
> > include in a 1.10.x.
> >
> > On Tue, Feb 23, 2021 at 9:44 AM Ryan Skraba <ry...@skraba.com> wrote:
> >
> > > Hello Avro community,
> > >
> > > We've kept up a decent cadence over the last few releases of every six
> > > months! At this rate, the next release would be in May for 1.11.0 (and
> > > we're looking forward to it -- seeya python2!)
> > >
> > > In the meantime, I was thinking it would be good to release another
> 1.10.2,
> > > specifically to help bump some downstream projects (see
> > > https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a
> bugfix
> > > release instead of 1.11.x for a couple of reasons: it would be ideal
> to get
> > > this out sooner rather than later, we're already seeing some interest
> and
> > > effort for bumping Avro, and it's reassuring for other projects to see
> > > bugfix releases.
> > >
> > > In my opinion, with experience it's getting easier to do these minor
> > > releases. I'd happily volunteer to shepherd this one through, and (as
> > > always) if anyone wants to shadow the process we can do it together.
> > >
> > > What do you think? Are there any other bugfixes that you'd like to
> see in
> > > a 1.10.x release?[1]
> > >
> > > Best regards, Ryan
> > >
> > > [1]
> > >
> > >
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
> > >
>
Re: [PROPOSAL] Let's prepare a 1.10.2
Posted by Ismaël Mejía <ie...@gmail.com>.
BIg +1 Ryan,
It definitely makes sense to have this release and is consistent with
what we have been doing in the last versions.
We should ideally also catch some dependency upgrades for the
javascript implementation if there is anyone with the expertise who
wants to contribute to this it will be great.
On Tue, Feb 23, 2021 at 3:57 PM Tim Perkins <tj...@gmail.com> wrote:
>
> There have been some recent Ruby performance fixes that would be good to
> include in a 1.10.x.
>
> On Tue, Feb 23, 2021 at 9:44 AM Ryan Skraba <ry...@skraba.com> wrote:
>
> > Hello Avro community,
> >
> > We've kept up a decent cadence over the last few releases of every six
> > months! At this rate, the next release would be in May for 1.11.0 (and
> > we're looking forward to it -- seeya python2!)
> >
> > In the meantime, I was thinking it would be good to release another 1.10.2,
> > specifically to help bump some downstream projects (see
> > https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a bugfix
> > release instead of 1.11.x for a couple of reasons: it would be ideal to get
> > this out sooner rather than later, we're already seeing some interest and
> > effort for bumping Avro, and it's reassuring for other projects to see
> > bugfix releases.
> >
> > In my opinion, with experience it's getting easier to do these minor
> > releases. I'd happily volunteer to shepherd this one through, and (as
> > always) if anyone wants to shadow the process we can do it together.
> >
> > What do you think? Are there any other bugfixes that you'd like to see in
> > a 1.10.x release?[1]
> >
> > Best regards, Ryan
> >
> > [1]
> >
> > https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
> >
Re: [PROPOSAL] Let's prepare a 1.10.2
Posted by Tim Perkins <tj...@gmail.com>.
There have been some recent Ruby performance fixes that would be good to
include in a 1.10.x.
On Tue, Feb 23, 2021 at 9:44 AM Ryan Skraba <ry...@skraba.com> wrote:
> Hello Avro community,
>
> We've kept up a decent cadence over the last few releases of every six
> months! At this rate, the next release would be in May for 1.11.0 (and
> we're looking forward to it -- seeya python2!)
>
> In the meantime, I was thinking it would be good to release another 1.10.2,
> specifically to help bump some downstream projects (see
> https://issues.apache.org/jira/browse/AVRO-3052). I'm proposing a bugfix
> release instead of 1.11.x for a couple of reasons: it would be ideal to get
> this out sooner rather than later, we're already seeing some interest and
> effort for bumping Avro, and it's reassuring for other projects to see
> bugfix releases.
>
> In my opinion, with experience it's getting easier to do these minor
> releases. I'd happily volunteer to shepherd this one through, and (as
> always) if anyone wants to shadow the process we can do it together.
>
> What do you think? Are there any other bugfixes that you'd like to see in
> a 1.10.x release?[1]
>
> Best regards, Ryan
>
> [1]
>
> https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.10.2
>