+1, thanks!

On Tue, Nov 10, 2026 at 12:42 PM Lucas Brutschy via dev
<[email protected]> wrote:
>
> Hi Matthias,
>
> thanks!
>
> I'm +1 for this proposal as well.
>
> Cheers,
> Lucas
>
> On Tue, Nov 10, 2026 at 3:31 AM Bill Bejeck <[email protected]> wrote:
> >
> > Hi Matthias,
> >
> > Thanks for putting this together.
> >
> > I'm +1 for this proposal.
> >
> > -Bill
> >
> >
> > On Mon, Nov 9, 2026 at 8:52 PM Matthias J. Sax via dev 
> > <[email protected]>
> > wrote:
> >
> > > Hello,
> > >
> > > after extensive discussions on this topic, I would like to call for a
> > > vote on the follow proposal:
> > >
> > >
> > >   - We do Kafka releases on a fixed time schedule, to avoid timeline
> > > drifts and to ensure that we are doing 3 release per year
> > >
> > >   - We want to accommodate major holidays across the globe, while trying
> > > to make every release roughly a 4-months cycle.
> > >
> > >   - We want to reduce the time windows between KIP, feature, and code
> > > freeze to ensure a more streamlines release delivery
> > >
> > >
> > > Concretely:
> > >
> > >   - We propose a 3 week window between KIP freeze and feature freeze
> > >
> > >   - We propose a 2 week window between feature freeze and code freeze
> > >
> > >   - KIP/feature/code freeze will each be on a Wednesday
> > >
> > >   - KIP freeze will be on fixed calendar weeks, namely
> > >     * week 9
> > >     * week 25
> > >     * week 41
> > >
> > >   - We will follow this new release cycle starting with the 4.7 release
> > >
> > >   - We already have a 4.5 release plan, and don't change it. KIP freeze
> > > is set to Jan/13/2027
> > >
> > >   - To transit into the new schedule, we will have KIP freeze for 4.6
> > > release on June/2/2027
> > >
> > >
> > > Outlook for 2028 (assuming we continue 4.x release series):
> > >
> > >    - AK 4.7 KIP freeze: March/9
> > >    - AK 4.8 KIP freeze: Jun/21
> > >    - AK 4.9 KIP freeze: Oct/11
> > >
> > >
> > > If this proposal gets accepted, we will update the corresponding release
> > > wiki pages accordingly.
> > >
> > >
> > > Thanks a lot,
> > >    -Matthias
> > >

Reply via email to