On Fri, Sep 15, 2023 at 7:43 PM Ryan Skraba <r...@skraba.com> wrote:
> And one month later... It looks like we're in a state OK to release > 1.11.3! There are no JIRA open on this FixVersion and I can build the > artifacts cleanly. I'm going to give this a start and try to get the > release candidates out this weekend, but because of the late notice, I > think it's fair to give some extra time to validate and vote during > the next week -- ideally before the Community over Code conference :D > > On the other hand, I'm having some trouble getting the website built > properly. This can be independent of the release artifacts, but > you'll notice that it's still on 1.11.1! If you have ideas on how we > can simplify this process, I'd love to hear them. > https://github.com/apache/avro/pull/2187 > > All my best, Ryan > > On Mon, Aug 14, 2023 at 2:14 PM Ryan Skraba <r...@skraba.com> wrote: > > > > Hey -- if nobody has any objections, I'd love to create the 1.11.3 this > week! > > > > Committers, if you've done any change to master that need to be in the > > 1.11.3 branch since the 1.11.2 release, make sure they've been > > cherry-picked and tested to the branch-1.11 :D > > > > I'll definitely go through the version bumps to make sure they're > > present (except for the jackson 2.15, I think we decided we would > > leave 1.11.x on 2.14.x until the next major release). > > > > Alll my best, Ryan > > > > On Tue, Aug 8, 2023 at 5:08 PM Andrei Leibovski > > <andrei.leibov...@appdirect.com.invalid> wrote: > > > > > > +1 > > > > > > Would be nice to have this out quickly, was trying to update Apache > Flink > > > to 1.11.2 and broke a bunch of tests because of AVRO-3789 > > > > > > 1.11.2 contains an important fix: > > > https://issues.apache.org/jira/browse/AVRO-3536 >
