Ah, I see Chris was faster writing this than me.

On Wed, May 15, 2024 at 6:43 PM Josep Prat <josep.p...@aiven.io> wrote:

> Hi all,
> You still have the full day of today (independently for the timezone) to
> get KIPs approved. Tomorrow morning (CEST timezone) I'll send another email
> asking developers to assign future approved KIPs to another version that is
> not 3.8.
>
> So, the only problem I see with KIP-1028 is that it hasn't been open for a
> vote for 72 hours (48 hours as of now). If there is no negative voting on
> the KIP I think we can let that one in, given it would only miss the
> deadline by less than 12 hours (if my timezone maths add up).
>
> Best,
>
> On Wed, May 15, 2024 at 6:35 PM Ismael Juma <m...@ismaeljuma.com> wrote:
>
>> The KIP freeze is just about having the KIP accepted. Not sure why we
>> would
>> need an exception for that.
>>
>> Ismael
>>
>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <fearthecel...@gmail.com>
>> wrote:
>>
>> > FWIW I think that the low blast radius for KIP-1028 should allow it to
>> > proceed without adhering to the usual KIP and feature freeze dates. Code
>> > freeze is probably worth still  respecting, at least if changes are
>> > required to the docker/jvm/Dockerfile. But I defer to Josep's judgement
>> as
>> > the release manager.
>> >
>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma <vedarth.sha...@gmail.com>
>> > wrote:
>> >
>> > > Hey Josep!
>> > >
>> > > The KIP 1028 has received the required votes. Voting thread:-
>> > > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
>> > > But we are keeping the vote open for 72 hours as per the process.
>> > >
>> > > I would like to request you to please consider it for the 3.8.0
>> release.
>> > >
>> > > Thanks and regards,
>> > > Vedarth
>> > >
>> > >
>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
>> <josep.p...@aiven.io.invalid>
>> > > wrote:
>> > >
>> > > > Hi Kafka developers!
>> > > >
>> > > > Today is the KIP freeze deadline. All KIPs should be accepted by EOD
>> > > today.
>> > > > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs
>> that
>> > > have
>> > > > been approved. Please any KIP approved after tomorrow should be
>> adopted
>> > > in
>> > > > a future release version, not 3.8.
>> > > >
>> > > > Other relevant upcoming deadlines:
>> > > > - Feature freeze is on May 29th
>> > > > - Code freeze is June 12th
>> > > >
>> > > > Best,
>> > > >
>> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat <josep.p...@aiven.io>
>> wrote:
>> > > >
>> > > > > Hi Kafka developers!
>> > > > > I just wanted to remind you all of the upcoming relevant dates for
>> > > Kafka
>> > > > > 3.8.0:
>> > > > > - KIP freeze is on May 15th (this is in a little less than 2
>> weeks)
>> > > > > - Feature freeze is on May 29th (this is in a little more than 25
>> > > days).
>> > > > >
>> > > > > If there is a KIP you really want to have in the 3.8 series, now
>> is
>> > the
>> > > > > time to make the last push. Once the deadline for KIP freeze is
>> over
>> > > I'll
>> > > > > update the release plan with the final list of KIPs accepted and
>> that
>> > > may
>> > > > > make it to the release.
>> > > > >
>> > > > > Best!
>> > > > >
>> > > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat <josep.p...@aiven.io>
>> > > wrote:
>> > > > >
>> > > > >> Hi all,
>> > > > >>
>> > > > >> Thanks for your support. I updated the skeleton release plan
>> created
>> > > by
>> > > > >> Colin. You can find it here:
>> > > > >>
>> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
>> > > > >>
>> > > > >> Our last release stumbled upon some problems while releasing and
>> was
>> > > > >> delayed by several weeks, so I won't try to shave some weeks from
>> > our
>> > > > plan
>> > > > >> for 3.8.0 (we might end up having delays again). Please raise
>> your
>> > > > concerns
>> > > > >> if you don't agree with the proposed dates.
>> > > > >>
>> > > > >> The current proposal on dates are:
>> > > > >>
>> > > > >>    - KIP Freeze: *15nd May *(Wednesday)
>> > > > >>       - A KIP must be accepted by this date in order to be
>> > considered
>> > > > >>       for this release. Note, any KIP that may not be implemented
>> > in a
>> > > > week, or
>> > > > >>       that might destabilize the release, should be deferred.
>> > > > >>    - Feature Freeze: *29th May *(Wednesday)
>> > > > >>       - *major features merged & working on stabilisation, minor
>> > > > >>       features have PR, release branch cut; anything not in this
>> > state
>> > > > will be
>> > > > >>       automatically moved to the next release in JIRA*
>> > > > >>    - Code Freeze: *12th June *(Wednesday)
>> > > > >>    - At least two weeks of stabilization will follow Code Freeze,
>> > > > >>    meaning we expect to release *no earlier* than *June 26th*. We
>> > will
>> > > > >>    move as fast as we can, and aim for completion the earliest we
>> > can
>> > > > in June.
>> > > > >>
>> > > > >> I went through the KIP list, and found that these are the ones
>> that
>> > > > might
>> > > > >> make it into the release:
>> > > > >> KIP-853: KRaft Controller Membership Changes (still under
>> > discussion)
>> > > > >> KIP-942: Add Power(ppc64le) support
>> > > > >> KIP-966: Eligible Leader Replicas
>> > > > >> KIP-974: Docker Image for GraalVM based Native Kafka Broker
>> > > > >> KIP-977: Partition-Level Throughput Metrics
>> > > > >> KIP-993: Allow restricting files accessed by File and Directory
>> > > > >> ConfigProviders
>> > > > >> KIP-994: Minor Enhancements to ListTransactions and
>> > > DescribeTransactions
>> > > > >> APIs
>> > > > >> KIP-996: Pre-Vote
>> > > > >> KIP-1004: Enforce tasks.max property in Kafka Connect
>> > > > >> KIP-1005: Expose EarliestLocalOffset and TieredOffset
>> > > > >> KIP-1007: Introduce Remote Storage Not Ready Exception
>> > > > >> KIP-1019: Expose method to determine Metric Measurability
>> > > > >>
>> > > > >> Please review the plan and provide any additional information or
>> > > updates
>> > > > >> regarding KIPs that target this release version (3.8).
>> > > > >> If you have authored any KIPs that have an inaccurate status in
>> the
>> > > > list,
>> > > > >> or are not in the list and should be, or are in the list and
>> should
>> > > not
>> > > > be
>> > > > >> - please share it in this thread so that I can keep the document
>> > > > accurate
>> > > > >> and up to date.
>> > > > >>
>> > > > >> Looking forward to your feedback.
>> > > > >>
>> > > > >> Best,
>> > > > >>
>> > > > >> On Wed, Feb 28, 2024 at 10:07 AM Satish Duggana <
>> > > > satish.dugg...@gmail.com>
>> > > > >> wrote:
>> > > > >>
>> > > > >>> Thanks Josep, +1.
>> > > > >>>
>> > > > >>> On Tue, 27 Feb 2024 at 17:29, Divij Vaidya <
>> > divijvaidy...@gmail.com>
>> > > > >>> wrote:
>> > > > >>> >
>> > > > >>> > Thank you for volunteering Josep. +1 from me.
>> > > > >>> >
>> > > > >>> > --
>> > > > >>> > Divij Vaidya
>> > > > >>> >
>> > > > >>> >
>> > > > >>> >
>> > > > >>> > On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna <
>> > cado...@apache.org>
>> > > > >>> wrote:
>> > > > >>> >
>> > > > >>> > > Thanks Josep!
>> > > > >>> > >
>> > > > >>> > > +1
>> > > > >>> > >
>> > > > >>> > > Best,
>> > > > >>> > > Bruno
>> > > > >>> > >
>> > > > >>> > > On 2/26/24 9:53 PM, Chris Egerton wrote:
>> > > > >>> > > > Thanks Josep, I'm +1 as well.
>> > > > >>> > > >
>> > > > >>> > > > On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
>> > > > >>> > > > <jols...@confluent.io.invalid> wrote:
>> > > > >>> > > >
>> > > > >>> > > >> Thanks Joesp. +1 from me.
>> > > > >>> > > >>
>> > > > >>> > > >> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat
>> > > > >>> <josep.p...@aiven.io.invalid
>> > > > >>> > > >
>> > > > >>> > > >> wrote:
>> > > > >>> > > >>
>> > > > >>> > > >>> Hi all,
>> > > > >>> > > >>>
>> > > > >>> > > >>> I'd like to volunteer as release manager for the Apache
>> > Kafka
>> > > > >>> 3.8.0
>> > > > >>> > > >>> release.
>> > > > >>> > > >>> If there are no objections, I'll start building a
>> release
>> > > plan
>> > > > >>> (or
>> > > > >>> > > >> adapting
>> > > > >>> > > >>> the one Colin made some weeks ago) in the wiki in the
>> next
>> > > > days.
>> > > > >>> > > >>>
>> > > > >>> > > >>> Thank you.
>> > > > >>> > > >>>
>> > > > >>> > > >>> --
>> > > > >>> > > >>> [image: Aiven] <https://www.aiven.io>
>> > > > >>> > > >>>
>> > > > >>> > > >>> *Josep Prat*
>> > > > >>> > > >>> Open Source Engineering Director, *Aiven*
>> > > > >>> > > >>> josep.p...@aiven.io   |   +491715557497
>> > > > >>> > > >>> aiven.io <https://www.aiven.io>   |   <
>> > > > >>> > > >> https://www.facebook.com/aivencloud
>> > > > >>> > > >>>>
>> > > > >>> > > >>>    <https://www.linkedin.com/company/aiven/>   <
>> > > > >>> > > >>> https://twitter.com/aiven_io>
>> > > > >>> > > >>> *Aiven Deutschland GmbH*
>> > > > >>> > > >>> Alexanderufer 3-7, 10117 Berlin
>> > > > >>> > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > > > >>> > > >>> Amtsgericht Charlottenburg, HRB 209739 B
>> > > > >>> > > >>>
>> > > > >>> > > >>
>> > > > >>> > > >
>> > > > >>> > >
>> > > > >>>
>> > > > >>
>> > > > >>
>> > > > >> --
>> > > > >> [image: Aiven] <https://www.aiven.io>
>> > > > >>
>> > > > >> *Josep Prat*
>> > > > >> Open Source Engineering Director, *Aiven*
>> > > > >> josep.p...@aiven.io   |   +491715557497
>> > > > >> aiven.io <https://www.aiven.io>   |
>> > > > >> <https://www.facebook.com/aivencloud>
>> > > > >> <https://www.linkedin.com/company/aiven/>
>> > > > >> <https://twitter.com/aiven_io>
>> > > > >> *Aiven Deutschland GmbH*
>> > > > >> Alexanderufer 3-7, 10117 Berlin
>> > > > >> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > > > >> Amtsgericht Charlottenburg, HRB 209739 B
>> > > > >>
>> > > > >
>> > > > >
>> > > > > --
>> > > > > [image: Aiven] <https://www.aiven.io>
>> > > > >
>> > > > > *Josep Prat*
>> > > > > Open Source Engineering Director, *Aiven*
>> > > > > josep.p...@aiven.io   |   +491715557497
>> > > > > aiven.io <https://www.aiven.io>   |
>> > > > > <https://www.facebook.com/aivencloud>
>> > > > > <https://www.linkedin.com/company/aiven/>   <
>> > > > https://twitter.com/aiven_io>
>> > > > > *Aiven Deutschland GmbH*
>> > > > > Alexanderufer 3-7, 10117 Berlin
>> > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > > > > Amtsgericht Charlottenburg, HRB 209739 B
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > [image: Aiven] <https://www.aiven.io>
>> > > >
>> > > > *Josep Prat*
>> > > > Open Source Engineering Director, *Aiven*
>> > > > josep.p...@aiven.io   |   +491715557497
>> > > > aiven.io <https://www.aiven.io>   |   <
>> > > https://www.facebook.com/aivencloud
>> > > > >
>> > > >   <https://www.linkedin.com/company/aiven/>   <
>> > > > https://twitter.com/aiven_io>
>> > > > *Aiven Deutschland GmbH*
>> > > > Alexanderufer 3-7, 10117 Berlin
>> > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > > > Amtsgericht Charlottenburg, HRB 209739 B
>> > > >
>> > >
>> >
>>
>
>
> --
> [image: Aiven] <https://www.aiven.io>
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io <https://www.aiven.io>   |
> <https://www.facebook.com/aivencloud>
> <https://www.linkedin.com/company/aiven/>   <https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>


-- 
[image: Aiven] <https://www.aiven.io>

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io <https://www.aiven.io>   |   <https://www.facebook.com/aivencloud>
  <https://www.linkedin.com/company/aiven/>   <https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Reply via email to