Hi all, Is there a documented process for creating a new release? Something which lists the steps involved including prerequisites, quality gates, etc. which would help volunteers?
Thanks, Krishnan On Wed, Oct 14, 2020 at 2:16 AM Ryan Skraba <r...@skraba.com> wrote: > Hello, great timing! > > I'd definitely like to see a new release. A minor 1.10.1 bug fix release > would probably be reassuring -- it looks like the idea of bumping the Avro > version in some downstream projects is getting a bit more traction. I > don't have any strong opinion yet whether 1.11.0 is ready or necessary. > > I just set AVRO-2817 to 1.10.1 since it breaks a Hive unit test. There's a > couple of other unresolved bugs to go through for 1.10.1, and it would be > great (as always) to catch up on any PRs that just need a bit of attention. > > I had the pleasure of working with the 1.9.2 release :D I'd be pleased to > either volunteer for 1.10.1 or to help out if anyone else wants to give it > a try! > > All my best, Ryan > > > > > On Wed, Oct 14, 2020 at 8:08 AM Sean Busbey <bus...@apache.org> wrote: > > > Hi folks! > > > > It's been a while since our last release. We've had some nice stuff > > land and we should get those contributions into releases so they are > > more widely available. > > > > Is there anything that I should consider a blocker on a 1.10.1 minor > > release off of branch-1.10? > > > > How about our next major release for 1.11.0? Is all the python 2 > > removal clean up in place now? > > > > Any volunteers available to lead things through our release process > > for either of these? > > > > -busbey > > >
