No problem, we can wait till a 1.13.0. If I'm needed for help, let me know. I'll start documenting the commands to publish the Gradle plugin.
Hielke On Wednesday, April 8th, 2026 at 18:18, Ryan Skraba <[email protected]> wrote: > I see what you mean! > > I think we're willing to learn how to release this correctly and your > help is invaluable. Please don't be discouraged if it doesn't happen > for 1.12.2; I'm hoping that we can get that out very rapidly as a step > to focus on a 1.13.0. I would love to see the gradle plugin as the > compelling reason to have people bump forward to 1.13.0! > > All my best, Ryan > > On Mon, 6 Apr 2026 at 18:44, H. de Vries <[email protected]> wrote: > > > > @Ryan > > | I'm not sure what "the release is cancelled" means... > > > > It means that there are not enough Avro people committed to releasing and > > maintaining the Gradle plugin. It's an extra step in the release process > > and maintenance will be needed. I hoped to convince everyone that the > > Gradle plugin is thoroughly tested, reviewed, and low-maintenance. It's > > also high in demand. I'm willing to do the maintenance and support, but I'm > > not an official committer (but I'm willing to become one!). > > > > Regards, > > > > Hielke > > > > > > On Monday, April 6th, 2026 at 18:30, Ryan Skraba <[email protected]> wrote: > > > > > OK, I have a PR for doing an Avro 1.12.2 release that incorporates > > > *all* of the version bumps but not all of the new fixes and features > > > that are on main. > > > > > > https://github.com/apache/avro/pull/3724 > > > > > > Wow, this is a painfully time-consumer process for something that is > > > essentially free with dependabot! I'm convinced that doing it > > > manually is the *wrong* thing to do if we were to want to release a > > > 1.11.6 (which doesn't seem useful if we're also going to push forward > > > to 1.13.0 ASAP for the gradle plugin). > > > > > > Does anybody know how to set up dependabot on multiple branches? > > > Let's get that going! > > > > > > I'm prioritizing version bumps... if there's anything else in 1.13.0 > > > that you'd like to see in 1.12.2, don't hesitate to give us a shout! > > > Otherwise I'll propose an RC1 in the next few days with what we have. > > > > > > All my best, Ryan > > > > > > On Mon, 6 Apr 2026 at 14:50, Ryan Skraba <[email protected]> wrote: > > > > > > > > Hello! I'm definitely present and motivated for voting on a release! > > > > > > > > I'm not sure what "the release is cancelled" means... we will > > > > definitely be having additional releases, and I'm all for including > > > > your work on the gradle plugin as soon as it's ready! > > > > > > > > I'd like to make a proposition however. I'd like to do the next > > > > 1.12.2 release immediately, with an eye on doing a 1.13.0 release > > > > almost directly afterwards. The big changes (including PHP and > > > > gradle) should be in the major 1.13.0 release. > > > > > > > > This will allow us to get some nice dependency bumps in the very short > > > > term that users are asking for. It's irritating how tricky the > > > > cherry-picks are to do these minor releases, so doing this right away > > > > will make it easier for the next major/minor releases. That being > > > > said, we can drop 1.11.x now if we're going to do a 1.13.0 in the new > > > > few weeks! > > > > > > > > I did a few hotfixes to get branch-1.12 back into releasable shape, > > > > and Ismael did a lot of work identifying the cherry-picks back to the > > > > branch-1.12. I've got some time this long weekend to apply them. > > > > Does anybody object to this strategy? > > > > > > > > I don't want it to look like doing a restricted 1.12.2 release is > > > > abandoning the 1.13.0 ! We appreciate the work being put into it of > > > > course! > > > > > > > > All my best, Ryan > > > > > > > > On Thu, 2 Apr 2026 at 16:38, H. de Vries <[email protected]> wrote: > > > > > > > > > > Hi team, > > > > > > > > > > We've been working on a high-in-demand Gradle plugin for quite a > > > > > while now. Gradle is getting more popular and there is a shift in use > > > > > from Maven to Gradle, likely because of the popularity of Kotlin. > > > > > Kotlin's main build tool is Gradle. > > > > > > > > > > The Avro Gradle plugin's code is reviewed by several engineers, > > > > > tested extensively, and run in production in the company I work for. > > > > > The code is low-maintenance and it just provides the same > > > > > functionality as the Maven plugin. The last step is making a release > > > > > for ASF. > > > > > > > > > > I was told today that the release is cancelled as it's hard to find > > > > > PMC members to do a release, and take responsibility of maintaining > > > > > it. I know of mgrigorov and Oscar willing to make a release, so I > > > > > guess that means we need one more PMC member? Can we do anything to > > > > > make a release happen? > > > > > > > > > > The Gradle plugin code is self-contained, so we don't have to build > > > > > the whole Java project. We need to someone with the credentials to > > > > > release to Gradle Plugin portal, and run one command to release it. > > > > > > > > > > I hope we can make it work. > > > > > > > > > > Regards, > > > > > > > > > > Hielke (frevib) > > > > > Gradle plugin code: https://github.com/apache/avro/pull/3614 > > > > > > > > > > On Friday, March 13th, 2026 at 13:02, Jean-Baptiste Onofré > > > > > <[email protected]> wrote: > > > > > > > > > > I meant 1.12.2 and 1.12.3 after. > > > > > > > > > > The gradle plugin should not be juist the binary gradle plugin. It > > > > > has to be included in the "official" release, including source > > > > > distribution. > > > > > > > > > > Regards > > > > > JB > > > > > > > > > > On Fri, Mar 13, 2026 at 12:33 PM Martin Grigorov > > > > > <[email protected]> wrote: > > > > >> > > > > >> > > > > >> > > > > >> On Fri, Mar 13, 2026 at 12:15 PM Jean-Baptiste Onofré > > > > >> <[email protected]> wrote: > > > > >>> > > > > >>> Hi Oscar > > > > >>> > > > > >>> I would propose to have 1.12.1 with the Gradle plugin. > > > > >>> For 1.12.1, I would like also to propose some dependencies updates. > > > > >>> I'm working on the check and PRs right now. > > > > >>> > > > > >>> The rest can come in a 1.12.2 release. > > > > >> > > > > >> > > > > >> JB, 1.12.1 was released some months ago. > > > > >> > > > > >> The question is whether to release just the new Gradle plugin at > > > > >> https://plugins.gradle.org/ or to make a complete release with > > > > >> whatever commits we have in all SDKs but the Rust one which is in > > > > >> separate repo with its own release cycle. > > > > >> > > > > >> I am for a complete 1.12.2 release! > > > > >>> > > > > >>> > > > > >>> Thoughts ? > > > > >>> > > > > >>> Regards > > > > >>> JB > > > > >>> > > > > >>> On Fri, Mar 13, 2026 at 11:03 AM Oscar Westra van Holthe - Kind > > > > >>> <[email protected]> wrote: > > > > >>>> > > > > >>>> Hi everyone, > > > > >>>> > > > > >>>> There have been quite a few dependency updates and a few changes, > > > > >>>> but also a few larger things that have popped up: > > > > >>>> 1. a Grade plugin for the Java SDK > > > > >>>> 2. modernization of the PHP codebase > > > > >>>> 3. a discussion on the future of Avro IPC > > > > >>>> > > > > >>>> Going forward, I'd like to release version 1.12.2 somewhere before > > > > >>>> the summer, including these things. > > > > >>>> > > > > >>>> Alternatively, as there is quite some demand for the Gradle > > > > >>>> plugin, we can release this as a late artefact for 1.12.1. > > > > >>>> > > > > >>>> What do you think? Should we aim for version 1.12.2? And if so, > > > > >>>> are there any things we should include? > > > > >>>> > > > > >>>> I'd love to hear your thoughts. > > > > >>>> > > > > >>>> > > > > >>>> Kind regards, > > > > >>>> Oscar > > > > >>>> > > > > >>>> -- > > > > >>>> ✉️ Oscar Westra van Holthe - Kind <[email protected]> > > > > >>>> 🌐 https://github.com/opwvhk/ > > > > > > > > > > > > > >
