I also think we can discuss when it turns out that we really need 4.1.1, for example, due to a critical CVE. Essentially, cherry-picking is not straightforward thanks to our recent excellent momentum and changes, such as JDK 21 or the restructuring of IMetaStoreClient. However, if it is genuinely essential, I can assist the community in making the decision and cutting a patch version.
Regards, Okumin On Thu, Jul 10, 2025 at 1:13 AM Ayush Saxena <ayush...@gmail.com> wrote: > > +1 to initiating the discussions once this is wrapped up. That said, I > echo the concerns raised by Stamatis — we simply don't have the > resources or bandwidth to maintain multiple release lines. We > shouldn't plan with 4.1.1 in mind from the outset. Instead, let’s keep > the door open for a potential 4.1.1 only if something critical comes > up in this release. > > Otherwise, the focus should shift toward 4.2.0, which can include more > substantial changes. Let’s treat 4.1.0 as a complete package, not > something that's expecting an immediate follow-up. > > Thanks, Butao, for sharing the release status. Looking forward to the RC :) > > –Ayush > > -Ayush > > On Wed, 9 Jul 2025 at 16:17, Denys Kuzmenko <dkuzme...@apache.org> wrote: > > > > Not sure. ideally, 4.1.1 should include the critical fixes. However, we > > might consider a major release that includes JDK 21 support, Iceberg > > auto-compaction, and other improvements from the master branch. > > > > But let’s discuss it once we get there.
