Hi Colin, > Do we feel that KIP-1040 can make feature freeze?
I think yes but it all depends on the review. In any case the changes are not so complex. Mario. On Wed, Jun 26, 2024 at 10:06 PM Colin McCabe <cmcc...@apache.org> wrote: > Hi Mario and Nelson, > > Thanks for asking. Both of these KIPs can certainly go in 3.9 if we can > hit the deadlines. If you need an extra day or two just ping me. (But I > don't want to extend things for too long!) :) > > Do we feel that KIP-1040 can make feature freeze? > > best, > Colin > > On Tue, Jun 25, 2024, at 01:48, Mario Fiore Vitale wrote: > > Hi all, > > > > Can the KIP-1040[1] be included? It is accepted and a PR review is in > > progress. > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1040%3A+Improve+handling+of+nullable+values+in+InsertField%2C+ExtractField%2C+and+other+transformations > > > > Thanks, > > Mario. > > > > > > On Tue, Jun 25, 2024 at 8:28 AM Nelson B. <bachmanity...@gmail.com> > wrote: > > > >> Hello, > >> > >> Can I include KIP-1025 > >> < > >> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1025%3A+Optionally+URL-encode+clientID+and+clientSecret+in+authorization+header > >> > > >> in > >> this release? > >> It's currently in the voting stage, I hope it can receive enough votes > by > >> next week. > >> > >> Thanks. > >> > >> On Tue, Jun 18, 2024 at 5:32 AM José Armando García Sancio > >> <jsan...@confluent.io.invalid> wrote: > >> > >> > Would it be better to start a DISCUSS thread for 4.0 and keep this > >> > thread for 3.9 discussions? We seem to have agreement on 3.9. > >> > > >> > On Mon, Jun 17, 2024 at 4:29 PM José Armando García Sancio > >> > <jsan...@confluent.io> wrote: > >> > > > >> > > +1 for me. Thanks Colin for volunteering to be the release manager. > >> > > > >> > > On Mon, Jun 17, 2024 at 4:15 PM Ismael Juma <m...@ismaeljuma.com> > wrote: > >> > > > > >> > > > Hi all, > >> > > > > >> > > > I think we should actually look at the target dates vs just > looking > >> at > >> > the > >> > > > release length. 3.9 is an August release. I suggest we aim for a > >> > November > >> > > > release for 4.0, which is 3 months (instead of 4). Why? Because > >> > December is > >> > > > a tricky month given holidays and all. And it gives us a buffer > for > >> > release > >> > > > delays that still allows for a 4.0 in 2024. > >> > > > > >> > > > Ismael > >> > > > > >> > > > On Mon, Jun 17, 2024 at 12:54 PM Matthias J. Sax < > mj...@apache.org> > >> > wrote: > >> > > > > >> > > > > In general I prefer to stick with the original time frame, but I > >> > believe > >> > > > > an additional month would be good for KIP-848. > >> > > > > > >> > > > > Maybe we can cut down 2 weeks for the 4.1 and 4.2 releases > each, to > >> > make > >> > > > > up for the time? Not a must; just an idea. We can also just > accept > >> a > >> > > > > one-time shift of the release time plan -- we did not really > lose > >> the > >> > > > > time effectively, as there was one additional release. > >> > > > > > >> > > > > > >> > > > > -Matthias > >> > > > > > >> > > > > > >> > > > > On 6/17/24 12:14 PM, David Jacot wrote: > >> > > > > > +1 for the release plan. Thanks! > >> > > > > > > >> > > > > > +1 for releasing 4.0 four months after 3.9. 4.0 is actually a > >> > pretty big > >> > > > > > release as we will GA KIP-848, including new group coordinator > >> and > >> > new > >> > > > > > consumer rebalance protocol. This is a pretty big change :). > >> > > > > > > >> > > > > > Best, > >> > > > > > David > >> > > > > > > >> > > > > > Le lun. 17 juin 2024 à 20:36, Colin McCabe < > cmcc...@apache.org> > >> a > >> > écrit > >> > > > > : > >> > > > > > > >> > > > > >> Hi all, > >> > > > > >> > >> > > > > >> Thanks, everyone. > >> > > > > >> > >> > > > > >> Quick update: on the release plan page, I moved feature > freeze > >> > forward > >> > > > > and > >> > > > > >> code freeze by one week to make sure we can hit that. No > other > >> > dates > >> > > > > >> changed. > >> > > > > >> > >> > > > > >> With regard to 4.0, I was assuming that we'd do it 4 months > >> after > >> > 3.9 > >> > > > > was > >> > > > > >> released. I think for that release, we should front-load all > the > >> > "remove > >> > > > > >> deprecated stuff" work that has piled up, and try to really > hit > >> > all the > >> > > > > >> release milestone dates. I don't think 4.0 needs to be a very > >> > ambitious > >> > > > > >> release, it really is mostly about the removals and the new > JDK > >> > (which > >> > > > > are > >> > > > > >> a big deal, but I hope should fit within the normal > timeframes). > >> > That > >> > > > > being > >> > > > > >> said, if people want a shorter 4.0, I'm open to that, as > long as > >> > we're > >> > > > > >> confident we could actually do that :) > >> > > > > >> > >> > > > > >> best, > >> > > > > >> Colin > >> > > > > >> > >> > > > > >> > >> > > > > >> On Fri, Jun 14, 2024, at 20:56, Sophie Blee-Goldman wrote: > >> > > > > >>> +1, thank you Colin > >> > > > > >>> > >> > > > > >>> Given the July freeze deadlines, I take it we are going with > >> the > >> > "short > >> > > > > >>> 3.9.0 release" option and that the existence of this release > >> will > >> > > > > impact > >> > > > > >>> the 4.0.0 deadlines which will still follow the usual > schedule > >> > -- in > >> > > > > >> other > >> > > > > >>> words, this is an "additional release" outside of the > regular > >> > timeline. > >> > > > > >> Is > >> > > > > >>> this understanding correct? > >> > > > > >>> > >> > > > > >>> On Fri, Jun 14, 2024 at 5:57 PM Chia-Ping Tsai < > >> > chia7...@gmail.com> > >> > > > > >> wrote: > >> > > > > >>> > >> > > > > >>>> +1 thanks Colin! > >> > > > > >>>> > >> > > > > >> > >> > > > > > > >> > > > > > >> > > > >> > > > >> > > > >> > > -- > >> > > -José > >> > > >> > > >> > > >> > -- > >> > -José > >> > > >> > > > > > > -- > > > > Mario Fiore Vitale > > > > Senior Software Engineer > > > > Red Hat <https://www.redhat.com/> > > <https://www.redhat.com/> > > -- Mario Fiore Vitale Senior Software Engineer Red Hat <https://www.redhat.com/> <https://www.redhat.com/>
