Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for the brief discussion Matthias and Israel.

Since there's no option but to merge a change, at this late stage in the
release process I'd agree with Matthias's suggestion to move forward with a
partial reversion of changes, which seems to be the safest of the two
options. I'll port the changes to the release plan and the blogpost I'm
preparing.

Hi Ron. Thanks for reporting the new issue. Indeed, we are quite picky
about what constitutes a blocker at this point. I was about to start
preparing the first RC earlier today.
The issue you report seems to meet our bar. Given that it's low risk, I'm
in favor of including it if we can merge the PR you prepared some time
soon.

Thank you all,
Konstantine

On Thu, Aug 19, 2021 at 6:09 PM Ron Dagostino  wrote:

> Hi Konstantine.  A potential 3.0 blocker was discovered today,
> https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13219.  The
> BrokerState metric is not working for KRaft clusters -- it always indicates
> that the broker is in the "not running" state.  A PR is available at
> https://github.com/apache/kafka/pull/11239.  The risk is low, and there is
> no workaround, but I also understand the bar for a blocker is pretty high
> at this point.
>
> Ron
>
> On Thu, Aug 19, 2021 at 5:54 PM Israel Ekpo  wrote:
>
> > Konstantine,
> >
> > After a brief chat with Sophie, I just updated the name for KIP-633 to be
> > more descriptive of what is actually happening in the implementation
> >
> > It is changed on the KIP page and the JIRA task title is also updated to
> be
> > more descriptive
> > https://cwiki.apache.org/confluence/x/Ho2NCg
> > https://issues.apache.org/jira/browse/KAFKA-8613
> >
> > However, I could not update the page for the 3.0 release plan. I do not
> > have the permissions for that update.
> > https://cwiki.apache.org/confluence/x/woONCg
> >
> > When you have a moment, please could you update the release plan for 3.0
> to
> > reflect the update name for the KIP?
> >
> > Thank you very much
> >
> > Sincerely,
> > Israel
> >
> >
> > On Thu, Aug 19, 2021 at 5:50 PM Israel Ekpo 
> wrote:
> >
> > > Hi Matthias, it is possible to still deprecate JoinWindows.of(size)
> even
> > > though the new join semantics is disabled.
> > >
> > > I just pre-recorded a talk for Kafka Summit Americas where I am
> > > recommending a switch to the new APIs instead of the deprecated one
> > > starting from 3.0
> > >
> > > I would love to be involved in the discussion for the fix so that we
> try
> > > to honor the expectations of the KIP as much as possible.
> > >
> > > So far, it looks like the PR will still honor the expectations of the
> KIP
> > >
> > > https://github.com/apache/kafka/pull/11235
> > >
> > > Thanks for sharing this to create awareness.
> > >
> > > Sincerely,
> > > Israel
> > >
> > >
> > >
> > >
> > >
> > > On Wed, Aug 18, 2021 at 8:57 PM Matthias J. Sax 
> > wrote:
> > >
> > >> Hi,
> > >>
> > >> we discovered a potential blocker for 3.0.0 today:
> > >> https://issues.apache.org/jira/browse/KAFKA-13216
> > >>
> > >> We are still evaluating a potential fix. If we cannot fix it quickly,
> > >> the fall-back would be to partially roll-back KIP-633, to disable the
> > >> new join semantics such that people cannot hit this bug.
> > >>
> > >> Thoughts?
> > >>
> > >>
> > >> -Matthias
> > >>
> > >>
> > >> On 8/17/21 1:29 PM, Konstantine Karantasis wrote:
> > >> > Hi Rajini.
> > >> >
> > >> > Approved, given its low risk and the lack of convenient workarounds.
> > >> >
> > >> > Konstantine
> > >> >
> > >> >
> > >> > On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram <
> > >> rajinisiva...@gmail.com>
> > >> > wrote:
> > >> >
> > >> >> Hi Konstantine,
> > >> >>
> > >> >> We found an issue with replication with IBP 2.7:
> > >> >> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is
> small
> > >> and
> > >> >> low
> > >> >> risk and has been merged to trunk. Can we include this in 3.0
> branch
> > >> since
> > >> >> it can result in IllegalStateException during replication?
> > >> >>
> > >> >> Thank you,
> > >> >>
> > >> >> Rajini
> > >> >>
> > >> >>
> > >> >> On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
> > >> >> kkaranta...@apache.org> wrote:
> > >> >>
> > >> >>> Jose, thanks for the heads up on the 3 new blocker candidates.
> > >> >>>
> > >> >>> I read the tickets and they have clear descriptions and
> > implementation
> > >> >>> details.
> > >> >>> However, at this stage to be able to make a call and approve new
> > >> blockers
> > >> >>> I'd appreciate it if we could get some insight regarding the risk
> > and
> > >> the
> > >> >>> necessity of a fix. A rough ETA would also be helpful.
> > >> >>>
> > >> >>> Having said that, based on the descriptions and the existence of a
> > few
> > >> >>> other blockers, I'm tentatively approving KAFKA-13161,
> KAFKA-13165,
> > >> and
> > >> >>> KAFKA-13168 and we might have to make a new assessment if these
> are
> > >> the
> > >> >>> only blockers in the next few days or if we notice a 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ron Dagostino]

Hi Konstantine.  A potential 3.0 blocker was discovered today,
https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13219.  The
BrokerState metric is not working for KRaft clusters -- it always indicates
that the broker is in the "not running" state.  A PR is available at
https://github.com/apache/kafka/pull/11239.  The risk is low, and there is
no workaround, but I also understand the bar for a blocker is pretty high
at this point.

Ron

On Thu, Aug 19, 2021 at 5:54 PM Israel Ekpo  wrote:

> Konstantine,
>
> After a brief chat with Sophie, I just updated the name for KIP-633 to be
> more descriptive of what is actually happening in the implementation
>
> It is changed on the KIP page and the JIRA task title is also updated to be
> more descriptive
> https://cwiki.apache.org/confluence/x/Ho2NCg
> https://issues.apache.org/jira/browse/KAFKA-8613
>
> However, I could not update the page for the 3.0 release plan. I do not
> have the permissions for that update.
> https://cwiki.apache.org/confluence/x/woONCg
>
> When you have a moment, please could you update the release plan for 3.0 to
> reflect the update name for the KIP?
>
> Thank you very much
>
> Sincerely,
> Israel
>
>
> On Thu, Aug 19, 2021 at 5:50 PM Israel Ekpo  wrote:
>
> > Hi Matthias, it is possible to still deprecate JoinWindows.of(size) even
> > though the new join semantics is disabled.
> >
> > I just pre-recorded a talk for Kafka Summit Americas where I am
> > recommending a switch to the new APIs instead of the deprecated one
> > starting from 3.0
> >
> > I would love to be involved in the discussion for the fix so that we try
> > to honor the expectations of the KIP as much as possible.
> >
> > So far, it looks like the PR will still honor the expectations of the KIP
> >
> > https://github.com/apache/kafka/pull/11235
> >
> > Thanks for sharing this to create awareness.
> >
> > Sincerely,
> > Israel
> >
> >
> >
> >
> >
> > On Wed, Aug 18, 2021 at 8:57 PM Matthias J. Sax 
> wrote:
> >
> >> Hi,
> >>
> >> we discovered a potential blocker for 3.0.0 today:
> >> https://issues.apache.org/jira/browse/KAFKA-13216
> >>
> >> We are still evaluating a potential fix. If we cannot fix it quickly,
> >> the fall-back would be to partially roll-back KIP-633, to disable the
> >> new join semantics such that people cannot hit this bug.
> >>
> >> Thoughts?
> >>
> >>
> >> -Matthias
> >>
> >>
> >> On 8/17/21 1:29 PM, Konstantine Karantasis wrote:
> >> > Hi Rajini.
> >> >
> >> > Approved, given its low risk and the lack of convenient workarounds.
> >> >
> >> > Konstantine
> >> >
> >> >
> >> > On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram <
> >> rajinisiva...@gmail.com>
> >> > wrote:
> >> >
> >> >> Hi Konstantine,
> >> >>
> >> >> We found an issue with replication with IBP 2.7:
> >> >> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small
> >> and
> >> >> low
> >> >> risk and has been merged to trunk. Can we include this in 3.0 branch
> >> since
> >> >> it can result in IllegalStateException during replication?
> >> >>
> >> >> Thank you,
> >> >>
> >> >> Rajini
> >> >>
> >> >>
> >> >> On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
> >> >> kkaranta...@apache.org> wrote:
> >> >>
> >> >>> Jose, thanks for the heads up on the 3 new blocker candidates.
> >> >>>
> >> >>> I read the tickets and they have clear descriptions and
> implementation
> >> >>> details.
> >> >>> However, at this stage to be able to make a call and approve new
> >> blockers
> >> >>> I'd appreciate it if we could get some insight regarding the risk
> and
> >> the
> >> >>> necessity of a fix. A rough ETA would also be helpful.
> >> >>>
> >> >>> Having said that, based on the descriptions and the existence of a
> few
> >> >>> other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165,
> >> and
> >> >>> KAFKA-13168 and we might have to make a new assessment if these are
> >> the
> >> >>> only blockers in the next few days or if we notice a regression
> during
> >> >>> testing.
> >> >>>
> >> >>> Konstantine
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
> >> >>> kkaranta...@apache.org> wrote:
> >> >>>
> >> 
> >>  Thanks for reporting this new issue Ryan,
> >> 
> >>  It's important and this issue seems to have clearly regressed
> dynamic
> >>  default configs in the 3.0 branch.
> >>  So, it's approved.
> >> 
> >>  Konstantine
> >> 
> >> 
> >>  On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
> >>   wrote:
> >> 
> >> > Hey all,
> >> >
> >> > For the KIP-500 work for 3.0 we would like to propose the
> following
> >> > Jiras as blockers:
> >> >
> >> > 1. https://issues.apache.org/jira/browse/KAFKA-13168
> >> > 2. https://issues.apache.org/jira/browse/KAFKA-13165
> >> > 3. https://issues.apache.org/jira/browse/KAFKA-13161
> >> >
> >> > The description for each Jira should have more details.
> >> >
> >> > Thanks,
> >> 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Matthias J. Sax]

Given the discussed upgrade path from the current join semantics to the
improved join semantics, I think it's best to partly revert KIP-633 for
3.0 release.

I prepared a PR for it: https://github.com/apache/kafka/pull/11233

The idea is to stay on `JoinWindows.of().grace()` and not add
`JoinWindows.ofTimeDifferenceAndGrace / NoGrace()`: this way users
cannot enable the spurious left/outer join fix and we are safe.

We can fix the join bug and complete KIP-633 in 3.1 release.

As we undo the deprecation for `JoinWindows.of()` and
`JoinWindows.grace()`, I assume your talk is still correct... I actually
also talked about the stream/stream join fix in Kafka Summit Europe this
yeer "advertising" the improved join semantics... So we are somewhat in
the same boat. Still think it's fine if it only ships in 3.1 instead of 3.0.

I understand that it is annoying to only ship a partially implemented
KIP, but I strongly believe it's the best way forward.


-Matthias


On 8/19/21 2:53 PM, Israel Ekpo wrote:
> Konstantine,
> 
> After a brief chat with Sophie, I just updated the name for KIP-633 to be
> more descriptive of what is actually happening in the implementation
> 
> It is changed on the KIP page and the JIRA task title is also updated to be
> more descriptive
> https://cwiki.apache.org/confluence/x/Ho2NCg
> https://issues.apache.org/jira/browse/KAFKA-8613
> 
> However, I could not update the page for the 3.0 release plan. I do not
> have the permissions for that update.
> https://cwiki.apache.org/confluence/x/woONCg
> 
> When you have a moment, please could you update the release plan for 3.0 to
> reflect the update name for the KIP?
> 
> Thank you very much
> 
> Sincerely,
> Israel
> 
> 
> On Thu, Aug 19, 2021 at 5:50 PM Israel Ekpo  wrote:
> 
>> Hi Matthias, it is possible to still deprecate JoinWindows.of(size) even
>> though the new join semantics is disabled.
>>
>> I just pre-recorded a talk for Kafka Summit Americas where I am
>> recommending a switch to the new APIs instead of the deprecated one
>> starting from 3.0
>>
>> I would love to be involved in the discussion for the fix so that we try
>> to honor the expectations of the KIP as much as possible.
>>
>> So far, it looks like the PR will still honor the expectations of the KIP
>>
>> https://github.com/apache/kafka/pull/11235
>>
>> Thanks for sharing this to create awareness.
>>
>> Sincerely,
>> Israel
>>
>>
>>
>>
>>
>> On Wed, Aug 18, 2021 at 8:57 PM Matthias J. Sax  wrote:
>>
>>> Hi,
>>>
>>> we discovered a potential blocker for 3.0.0 today:
>>> https://issues.apache.org/jira/browse/KAFKA-13216
>>>
>>> We are still evaluating a potential fix. If we cannot fix it quickly,
>>> the fall-back would be to partially roll-back KIP-633, to disable the
>>> new join semantics such that people cannot hit this bug.
>>>
>>> Thoughts?
>>>
>>>
>>> -Matthias
>>>
>>>
>>> On 8/17/21 1:29 PM, Konstantine Karantasis wrote:
 Hi Rajini.

 Approved, given its low risk and the lack of convenient workarounds.

 Konstantine


 On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram <
>>> rajinisiva...@gmail.com>
 wrote:

> Hi Konstantine,
>
> We found an issue with replication with IBP 2.7:
> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small
>>> and
> low
> risk and has been merged to trunk. Can we include this in 3.0 branch
>>> since
> it can result in IllegalStateException during replication?
>
> Thank you,
>
> Rajini
>
>
> On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
> kkaranta...@apache.org> wrote:
>
>> Jose, thanks for the heads up on the 3 new blocker candidates.
>>
>> I read the tickets and they have clear descriptions and implementation
>> details.
>> However, at this stage to be able to make a call and approve new
>>> blockers
>> I'd appreciate it if we could get some insight regarding the risk and
>>> the
>> necessity of a fix. A rough ETA would also be helpful.
>>
>> Having said that, based on the descriptions and the existence of a few
>> other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165,
>>> and
>> KAFKA-13168 and we might have to make a new assessment if these are
>>> the
>> only blockers in the next few days or if we notice a regression during
>> testing.
>>
>> Konstantine
>>
>>
>>
>> On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
>> kkaranta...@apache.org> wrote:
>>
>>>
>>> Thanks for reporting this new issue Ryan,
>>>
>>> It's important and this issue seems to have clearly regressed dynamic
>>> default configs in the 3.0 branch.
>>> So, it's approved.
>>>
>>> Konstantine
>>>
>>>
>>> On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
>>>  wrote:
>>>
 Hey all,

 For the KIP-500 work for 3.0 we would like to propose the following
 Jiras 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Israel Ekpo]

Konstantine,

After a brief chat with Sophie, I just updated the name for KIP-633 to be
more descriptive of what is actually happening in the implementation

It is changed on the KIP page and the JIRA task title is also updated to be
more descriptive
https://cwiki.apache.org/confluence/x/Ho2NCg
https://issues.apache.org/jira/browse/KAFKA-8613

However, I could not update the page for the 3.0 release plan. I do not
have the permissions for that update.
https://cwiki.apache.org/confluence/x/woONCg

When you have a moment, please could you update the release plan for 3.0 to
reflect the update name for the KIP?

Thank you very much

Sincerely,
Israel


On Thu, Aug 19, 2021 at 5:50 PM Israel Ekpo  wrote:

> Hi Matthias, it is possible to still deprecate JoinWindows.of(size) even
> though the new join semantics is disabled.
>
> I just pre-recorded a talk for Kafka Summit Americas where I am
> recommending a switch to the new APIs instead of the deprecated one
> starting from 3.0
>
> I would love to be involved in the discussion for the fix so that we try
> to honor the expectations of the KIP as much as possible.
>
> So far, it looks like the PR will still honor the expectations of the KIP
>
> https://github.com/apache/kafka/pull/11235
>
> Thanks for sharing this to create awareness.
>
> Sincerely,
> Israel
>
>
>
>
>
> On Wed, Aug 18, 2021 at 8:57 PM Matthias J. Sax  wrote:
>
>> Hi,
>>
>> we discovered a potential blocker for 3.0.0 today:
>> https://issues.apache.org/jira/browse/KAFKA-13216
>>
>> We are still evaluating a potential fix. If we cannot fix it quickly,
>> the fall-back would be to partially roll-back KIP-633, to disable the
>> new join semantics such that people cannot hit this bug.
>>
>> Thoughts?
>>
>>
>> -Matthias
>>
>>
>> On 8/17/21 1:29 PM, Konstantine Karantasis wrote:
>> > Hi Rajini.
>> >
>> > Approved, given its low risk and the lack of convenient workarounds.
>> >
>> > Konstantine
>> >
>> >
>> > On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram <
>> rajinisiva...@gmail.com>
>> > wrote:
>> >
>> >> Hi Konstantine,
>> >>
>> >> We found an issue with replication with IBP 2.7:
>> >> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small
>> and
>> >> low
>> >> risk and has been merged to trunk. Can we include this in 3.0 branch
>> since
>> >> it can result in IllegalStateException during replication?
>> >>
>> >> Thank you,
>> >>
>> >> Rajini
>> >>
>> >>
>> >> On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
>> >> kkaranta...@apache.org> wrote:
>> >>
>> >>> Jose, thanks for the heads up on the 3 new blocker candidates.
>> >>>
>> >>> I read the tickets and they have clear descriptions and implementation
>> >>> details.
>> >>> However, at this stage to be able to make a call and approve new
>> blockers
>> >>> I'd appreciate it if we could get some insight regarding the risk and
>> the
>> >>> necessity of a fix. A rough ETA would also be helpful.
>> >>>
>> >>> Having said that, based on the descriptions and the existence of a few
>> >>> other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165,
>> and
>> >>> KAFKA-13168 and we might have to make a new assessment if these are
>> the
>> >>> only blockers in the next few days or if we notice a regression during
>> >>> testing.
>> >>>
>> >>> Konstantine
>> >>>
>> >>>
>> >>>
>> >>> On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
>> >>> kkaranta...@apache.org> wrote:
>> >>>
>> 
>>  Thanks for reporting this new issue Ryan,
>> 
>>  It's important and this issue seems to have clearly regressed dynamic
>>  default configs in the 3.0 branch.
>>  So, it's approved.
>> 
>>  Konstantine
>> 
>> 
>>  On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
>>   wrote:
>> 
>> > Hey all,
>> >
>> > For the KIP-500 work for 3.0 we would like to propose the following
>> > Jiras as blockers:
>> >
>> > 1. https://issues.apache.org/jira/browse/KAFKA-13168
>> > 2. https://issues.apache.org/jira/browse/KAFKA-13165
>> > 3. https://issues.apache.org/jira/browse/KAFKA-13161
>> >
>> > The description for each Jira should have more details.
>> >
>> > Thanks,
>> > -Jose
>> >
>> > On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
>> >  wrote:
>> >>
>> >> Hi Konstantine,
>> >>
>> >> I would like to report another bug in KRaft.
>> >>
>> >> The ConfigHandler that processes dynamic broker config deltas in
>> >> KRaft
>> >> expects that the default resource name for dynamic broker configs
>> is
>> >>> the
>> >> old default entity name used in ZK: "". Since dynamic
>> >> default
>> >> broker configs are persisted as empty string in the quorum instead
>> >> of
>> >> "", the brokers are not updating the their default
>> > configuration
>> >> when they see empty string as a resource name in the config delta
>> >> and
>> > are
>> >> throwing a NumberFormatException when they try to parse 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Israel Ekpo]

Hi Matthias, it is possible to still deprecate JoinWindows.of(size) even
though the new join semantics is disabled.

I just pre-recorded a talk for Kafka Summit Americas where I am
recommending a switch to the new APIs instead of the deprecated one
starting from 3.0

I would love to be involved in the discussion for the fix so that we try to
honor the expectations of the KIP as much as possible.

So far, it looks like the PR will still honor the expectations of the KIP

https://github.com/apache/kafka/pull/11235

Thanks for sharing this to create awareness.

Sincerely,
Israel





On Wed, Aug 18, 2021 at 8:57 PM Matthias J. Sax  wrote:

> Hi,
>
> we discovered a potential blocker for 3.0.0 today:
> https://issues.apache.org/jira/browse/KAFKA-13216
>
> We are still evaluating a potential fix. If we cannot fix it quickly,
> the fall-back would be to partially roll-back KIP-633, to disable the
> new join semantics such that people cannot hit this bug.
>
> Thoughts?
>
>
> -Matthias
>
>
> On 8/17/21 1:29 PM, Konstantine Karantasis wrote:
> > Hi Rajini.
> >
> > Approved, given its low risk and the lack of convenient workarounds.
> >
> > Konstantine
> >
> >
> > On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram  >
> > wrote:
> >
> >> Hi Konstantine,
> >>
> >> We found an issue with replication with IBP 2.7:
> >> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small and
> >> low
> >> risk and has been merged to trunk. Can we include this in 3.0 branch
> since
> >> it can result in IllegalStateException during replication?
> >>
> >> Thank you,
> >>
> >> Rajini
> >>
> >>
> >> On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
> >> kkaranta...@apache.org> wrote:
> >>
> >>> Jose, thanks for the heads up on the 3 new blocker candidates.
> >>>
> >>> I read the tickets and they have clear descriptions and implementation
> >>> details.
> >>> However, at this stage to be able to make a call and approve new
> blockers
> >>> I'd appreciate it if we could get some insight regarding the risk and
> the
> >>> necessity of a fix. A rough ETA would also be helpful.
> >>>
> >>> Having said that, based on the descriptions and the existence of a few
> >>> other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165, and
> >>> KAFKA-13168 and we might have to make a new assessment if these are the
> >>> only blockers in the next few days or if we notice a regression during
> >>> testing.
> >>>
> >>> Konstantine
> >>>
> >>>
> >>>
> >>> On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
> >>> kkaranta...@apache.org> wrote:
> >>>
> 
>  Thanks for reporting this new issue Ryan,
> 
>  It's important and this issue seems to have clearly regressed dynamic
>  default configs in the 3.0 branch.
>  So, it's approved.
> 
>  Konstantine
> 
> 
>  On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
>   wrote:
> 
> > Hey all,
> >
> > For the KIP-500 work for 3.0 we would like to propose the following
> > Jiras as blockers:
> >
> > 1. https://issues.apache.org/jira/browse/KAFKA-13168
> > 2. https://issues.apache.org/jira/browse/KAFKA-13165
> > 3. https://issues.apache.org/jira/browse/KAFKA-13161
> >
> > The description for each Jira should have more details.
> >
> > Thanks,
> > -Jose
> >
> > On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
> >  wrote:
> >>
> >> Hi Konstantine,
> >>
> >> I would like to report another bug in KRaft.
> >>
> >> The ConfigHandler that processes dynamic broker config deltas in
> >> KRaft
> >> expects that the default resource name for dynamic broker configs is
> >>> the
> >> old default entity name used in ZK: "". Since dynamic
> >> default
> >> broker configs are persisted as empty string in the quorum instead
> >> of
> >> "", the brokers are not updating the their default
> > configuration
> >> when they see empty string as a resource name in the config delta
> >> and
> > are
> >> throwing a NumberFormatException when they try to parse the resource
> > name
> >> to process it as a per-broker configuration.
> >>
> >> I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160
> >>
> >> I also have a PR to fix this:
> > https://github.com/apache/kafka/pull/11168
> >>
> >> I think that this should be a blocker for 3.0 because dynamic
> >> default
> >> broker configs will not be usable in KRaft otherwise.
> >>
> >> Best,
> >> Ryan Dielhenn
> >>
> >> On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
> >> kkaranta...@apache.org> wrote:
> >>
> >>> Thanks Ryan,
> >>>
> >>> Approved. Seems also like a low risk fix.
> >>> With that opportunity, let's make sure there are no other configs
> >>> that
> >>> would need a similar validation.
> >>>
> >>> Konstantine
> >>>
> >>> On Fri, Jul 30, 2021 at 8:33 AM Ryan 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Matthias J. Sax]

Hi,

we discovered a potential blocker for 3.0.0 today:
https://issues.apache.org/jira/browse/KAFKA-13216

We are still evaluating a potential fix. If we cannot fix it quickly,
the fall-back would be to partially roll-back KIP-633, to disable the
new join semantics such that people cannot hit this bug.

Thoughts?


-Matthias


On 8/17/21 1:29 PM, Konstantine Karantasis wrote:
> Hi Rajini.
> 
> Approved, given its low risk and the lack of convenient workarounds.
> 
> Konstantine
> 
> 
> On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram 
> wrote:
> 
>> Hi Konstantine,
>>
>> We found an issue with replication with IBP 2.7:
>> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small and
>> low
>> risk and has been merged to trunk. Can we include this in 3.0 branch since
>> it can result in IllegalStateException during replication?
>>
>> Thank you,
>>
>> Rajini
>>
>>
>> On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
>> kkaranta...@apache.org> wrote:
>>
>>> Jose, thanks for the heads up on the 3 new blocker candidates.
>>>
>>> I read the tickets and they have clear descriptions and implementation
>>> details.
>>> However, at this stage to be able to make a call and approve new blockers
>>> I'd appreciate it if we could get some insight regarding the risk and the
>>> necessity of a fix. A rough ETA would also be helpful.
>>>
>>> Having said that, based on the descriptions and the existence of a few
>>> other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165, and
>>> KAFKA-13168 and we might have to make a new assessment if these are the
>>> only blockers in the next few days or if we notice a regression during
>>> testing.
>>>
>>> Konstantine
>>>
>>>
>>>
>>> On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
>>> kkaranta...@apache.org> wrote:
>>>

 Thanks for reporting this new issue Ryan,

 It's important and this issue seems to have clearly regressed dynamic
 default configs in the 3.0 branch.
 So, it's approved.

 Konstantine


 On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
  wrote:

> Hey all,
>
> For the KIP-500 work for 3.0 we would like to propose the following
> Jiras as blockers:
>
> 1. https://issues.apache.org/jira/browse/KAFKA-13168
> 2. https://issues.apache.org/jira/browse/KAFKA-13165
> 3. https://issues.apache.org/jira/browse/KAFKA-13161
>
> The description for each Jira should have more details.
>
> Thanks,
> -Jose
>
> On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
>  wrote:
>>
>> Hi Konstantine,
>>
>> I would like to report another bug in KRaft.
>>
>> The ConfigHandler that processes dynamic broker config deltas in
>> KRaft
>> expects that the default resource name for dynamic broker configs is
>>> the
>> old default entity name used in ZK: "". Since dynamic
>> default
>> broker configs are persisted as empty string in the quorum instead
>> of
>> "", the brokers are not updating the their default
> configuration
>> when they see empty string as a resource name in the config delta
>> and
> are
>> throwing a NumberFormatException when they try to parse the resource
> name
>> to process it as a per-broker configuration.
>>
>> I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160
>>
>> I also have a PR to fix this:
> https://github.com/apache/kafka/pull/11168
>>
>> I think that this should be a blocker for 3.0 because dynamic
>> default
>> broker configs will not be usable in KRaft otherwise.
>>
>> Best,
>> Ryan Dielhenn
>>
>> On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
>> kkaranta...@apache.org> wrote:
>>
>>> Thanks Ryan,
>>>
>>> Approved. Seems also like a low risk fix.
>>> With that opportunity, let's make sure there are no other configs
>>> that
>>> would need a similar validation.
>>>
>>> Konstantine
>>>
>>> On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
>>>  wrote:
>>>
 Hey Konstantine,

 Thanks for the question. If these configs are not validated the
> user's
 experience will be affected and upgrades from 3.0 will be
>> harder.

 Best,
 Ryan Dielhenn

 On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
 kkaranta...@apache.org> wrote:

> Thanks for reporting this issue Ryan.
>
> I believe what you mention corresponds to the ticket you
>> created
> here:
>
>>> https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
>
> What happens if the configurations are present but the broker
> doesn't
 fail
> at startup when configured to run in KRaft mode?
> Asking to see if we have any workarounds in our availability.
>
> Thanks,
> Konstantine

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi Rajini.

Approved, given its low risk and the lack of convenient workarounds.

Konstantine


On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram 
wrote:

> Hi Konstantine,
>
> We found an issue with replication with IBP 2.7:
> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small and
> low
> risk and has been merged to trunk. Can we include this in 3.0 branch since
> it can result in IllegalStateException during replication?
>
> Thank you,
>
> Rajini
>
>
> On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
> kkaranta...@apache.org> wrote:
>
> > Jose, thanks for the heads up on the 3 new blocker candidates.
> >
> > I read the tickets and they have clear descriptions and implementation
> > details.
> > However, at this stage to be able to make a call and approve new blockers
> > I'd appreciate it if we could get some insight regarding the risk and the
> > necessity of a fix. A rough ETA would also be helpful.
> >
> > Having said that, based on the descriptions and the existence of a few
> > other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165, and
> > KAFKA-13168 and we might have to make a new assessment if these are the
> > only blockers in the next few days or if we notice a regression during
> > testing.
> >
> > Konstantine
> >
> >
> >
> > On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
> > kkaranta...@apache.org> wrote:
> >
> > >
> > > Thanks for reporting this new issue Ryan,
> > >
> > > It's important and this issue seems to have clearly regressed dynamic
> > > default configs in the 3.0 branch.
> > > So, it's approved.
> > >
> > > Konstantine
> > >
> > >
> > > On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
> > >  wrote:
> > >
> > >> Hey all,
> > >>
> > >> For the KIP-500 work for 3.0 we would like to propose the following
> > >> Jiras as blockers:
> > >>
> > >> 1. https://issues.apache.org/jira/browse/KAFKA-13168
> > >> 2. https://issues.apache.org/jira/browse/KAFKA-13165
> > >> 3. https://issues.apache.org/jira/browse/KAFKA-13161
> > >>
> > >> The description for each Jira should have more details.
> > >>
> > >> Thanks,
> > >> -Jose
> > >>
> > >> On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
> > >>  wrote:
> > >> >
> > >> > Hi Konstantine,
> > >> >
> > >> > I would like to report another bug in KRaft.
> > >> >
> > >> > The ConfigHandler that processes dynamic broker config deltas in
> KRaft
> > >> > expects that the default resource name for dynamic broker configs is
> > the
> > >> > old default entity name used in ZK: "". Since dynamic
> default
> > >> > broker configs are persisted as empty string in the quorum instead
> of
> > >> > "", the brokers are not updating the their default
> > >> configuration
> > >> > when they see empty string as a resource name in the config delta
> and
> > >> are
> > >> > throwing a NumberFormatException when they try to parse the resource
> > >> name
> > >> > to process it as a per-broker configuration.
> > >> >
> > >> > I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160
> > >> >
> > >> > I also have a PR to fix this:
> > >> https://github.com/apache/kafka/pull/11168
> > >> >
> > >> > I think that this should be a blocker for 3.0 because dynamic
> default
> > >> > broker configs will not be usable in KRaft otherwise.
> > >> >
> > >> > Best,
> > >> > Ryan Dielhenn
> > >> >
> > >> > On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
> > >> > kkaranta...@apache.org> wrote:
> > >> >
> > >> > > Thanks Ryan,
> > >> > >
> > >> > > Approved. Seems also like a low risk fix.
> > >> > > With that opportunity, let's make sure there are no other configs
> > that
> > >> > > would need a similar validation.
> > >> > >
> > >> > > Konstantine
> > >> > >
> > >> > > On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
> > >> > >  wrote:
> > >> > >
> > >> > > > Hey Konstantine,
> > >> > > >
> > >> > > > Thanks for the question. If these configs are not validated the
> > >> user's
> > >> > > > experience will be affected and upgrades from 3.0 will be
> harder.
> > >> > > >
> > >> > > > Best,
> > >> > > > Ryan Dielhenn
> > >> > > >
> > >> > > > On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
> > >> > > > kkaranta...@apache.org> wrote:
> > >> > > >
> > >> > > > > Thanks for reporting this issue Ryan.
> > >> > > > >
> > >> > > > > I believe what you mention corresponds to the ticket you
> created
> > >> here:
> > >> > > > >
> > https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
> > >> > > > >
> > >> > > > > What happens if the configurations are present but the broker
> > >> doesn't
> > >> > > > fail
> > >> > > > > at startup when configured to run in KRaft mode?
> > >> > > > > Asking to see if we have any workarounds in our availability.
> > >> > > > >
> > >> > > > > Thanks,
> > >> > > > > Konstantine
> > >> > > > >
> > >> > > > > On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
> > >> > > > >  wrote:
> > >> > > > >
> > >> > > > > > Hi,
> > >> > > > > >
> > >> > > > > > Disregard log.clean.policy being 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Rajini Sivaram]

Hi Konstantine,

We found an issue with replication with IBP 2.7:
https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small and low
risk and has been merged to trunk. Can we include this in 3.0 branch since
it can result in IllegalStateException during replication?

Thank you,

Rajini


On Thu, Aug 5, 2021 at 6:21 PM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

> Jose, thanks for the heads up on the 3 new blocker candidates.
>
> I read the tickets and they have clear descriptions and implementation
> details.
> However, at this stage to be able to make a call and approve new blockers
> I'd appreciate it if we could get some insight regarding the risk and the
> necessity of a fix. A rough ETA would also be helpful.
>
> Having said that, based on the descriptions and the existence of a few
> other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165, and
> KAFKA-13168 and we might have to make a new assessment if these are the
> only blockers in the next few days or if we notice a regression during
> testing.
>
> Konstantine
>
>
>
> On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
> kkaranta...@apache.org> wrote:
>
> >
> > Thanks for reporting this new issue Ryan,
> >
> > It's important and this issue seems to have clearly regressed dynamic
> > default configs in the 3.0 branch.
> > So, it's approved.
> >
> > Konstantine
> >
> >
> > On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
> >  wrote:
> >
> >> Hey all,
> >>
> >> For the KIP-500 work for 3.0 we would like to propose the following
> >> Jiras as blockers:
> >>
> >> 1. https://issues.apache.org/jira/browse/KAFKA-13168
> >> 2. https://issues.apache.org/jira/browse/KAFKA-13165
> >> 3. https://issues.apache.org/jira/browse/KAFKA-13161
> >>
> >> The description for each Jira should have more details.
> >>
> >> Thanks,
> >> -Jose
> >>
> >> On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
> >>  wrote:
> >> >
> >> > Hi Konstantine,
> >> >
> >> > I would like to report another bug in KRaft.
> >> >
> >> > The ConfigHandler that processes dynamic broker config deltas in KRaft
> >> > expects that the default resource name for dynamic broker configs is
> the
> >> > old default entity name used in ZK: "". Since dynamic default
> >> > broker configs are persisted as empty string in the quorum instead of
> >> > "", the brokers are not updating the their default
> >> configuration
> >> > when they see empty string as a resource name in the config delta and
> >> are
> >> > throwing a NumberFormatException when they try to parse the resource
> >> name
> >> > to process it as a per-broker configuration.
> >> >
> >> > I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160
> >> >
> >> > I also have a PR to fix this:
> >> https://github.com/apache/kafka/pull/11168
> >> >
> >> > I think that this should be a blocker for 3.0 because dynamic default
> >> > broker configs will not be usable in KRaft otherwise.
> >> >
> >> > Best,
> >> > Ryan Dielhenn
> >> >
> >> > On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
> >> > kkaranta...@apache.org> wrote:
> >> >
> >> > > Thanks Ryan,
> >> > >
> >> > > Approved. Seems also like a low risk fix.
> >> > > With that opportunity, let's make sure there are no other configs
> that
> >> > > would need a similar validation.
> >> > >
> >> > > Konstantine
> >> > >
> >> > > On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
> >> > >  wrote:
> >> > >
> >> > > > Hey Konstantine,
> >> > > >
> >> > > > Thanks for the question. If these configs are not validated the
> >> user's
> >> > > > experience will be affected and upgrades from 3.0 will be harder.
> >> > > >
> >> > > > Best,
> >> > > > Ryan Dielhenn
> >> > > >
> >> > > > On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
> >> > > > kkaranta...@apache.org> wrote:
> >> > > >
> >> > > > > Thanks for reporting this issue Ryan.
> >> > > > >
> >> > > > > I believe what you mention corresponds to the ticket you created
> >> here:
> >> > > > >
> https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
> >> > > > >
> >> > > > > What happens if the configurations are present but the broker
> >> doesn't
> >> > > > fail
> >> > > > > at startup when configured to run in KRaft mode?
> >> > > > > Asking to see if we have any workarounds in our availability.
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Konstantine
> >> > > > >
> >> > > > > On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
> >> > > > >  wrote:
> >> > > > >
> >> > > > > > Hi,
> >> > > > > >
> >> > > > > > Disregard log.clean.policy being included in this blocker.
> >> > > > > >
> >> > > > > > Best,
> >> > > > > > Ryan Dielhenn
> >> > > > > >
> >> > > > > > On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn <
> >> > > rdielh...@confluent.io>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > Hey Konstantine,
> >> > > > > > >
> >> > > > > > > I'd like to report another bug in KRaft.
> >> > > > > > >
> >> > > > > > > log.cleanup.policy, alter.config.policy.class.name, and
> >> > > > 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Jose, thanks for the heads up on the 3 new blocker candidates.

I read the tickets and they have clear descriptions and implementation
details.
However, at this stage to be able to make a call and approve new blockers
I'd appreciate it if we could get some insight regarding the risk and the
necessity of a fix. A rough ETA would also be helpful.

Having said that, based on the descriptions and the existence of a few
other blockers, I'm tentatively approving KAFKA-13161, KAFKA-13165, and
KAFKA-13168 and we might have to make a new assessment if these are the
only blockers in the next few days or if we notice a regression during
testing.

Konstantine



On Thu, Aug 5, 2021 at 10:04 AM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

>
> Thanks for reporting this new issue Ryan,
>
> It's important and this issue seems to have clearly regressed dynamic
> default configs in the 3.0 branch.
> So, it's approved.
>
> Konstantine
>
>
> On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
>  wrote:
>
>> Hey all,
>>
>> For the KIP-500 work for 3.0 we would like to propose the following
>> Jiras as blockers:
>>
>> 1. https://issues.apache.org/jira/browse/KAFKA-13168
>> 2. https://issues.apache.org/jira/browse/KAFKA-13165
>> 3. https://issues.apache.org/jira/browse/KAFKA-13161
>>
>> The description for each Jira should have more details.
>>
>> Thanks,
>> -Jose
>>
>> On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
>>  wrote:
>> >
>> > Hi Konstantine,
>> >
>> > I would like to report another bug in KRaft.
>> >
>> > The ConfigHandler that processes dynamic broker config deltas in KRaft
>> > expects that the default resource name for dynamic broker configs is the
>> > old default entity name used in ZK: "". Since dynamic default
>> > broker configs are persisted as empty string in the quorum instead of
>> > "", the brokers are not updating the their default
>> configuration
>> > when they see empty string as a resource name in the config delta and
>> are
>> > throwing a NumberFormatException when they try to parse the resource
>> name
>> > to process it as a per-broker configuration.
>> >
>> > I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160
>> >
>> > I also have a PR to fix this:
>> https://github.com/apache/kafka/pull/11168
>> >
>> > I think that this should be a blocker for 3.0 because dynamic default
>> > broker configs will not be usable in KRaft otherwise.
>> >
>> > Best,
>> > Ryan Dielhenn
>> >
>> > On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
>> > kkaranta...@apache.org> wrote:
>> >
>> > > Thanks Ryan,
>> > >
>> > > Approved. Seems also like a low risk fix.
>> > > With that opportunity, let's make sure there are no other configs that
>> > > would need a similar validation.
>> > >
>> > > Konstantine
>> > >
>> > > On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
>> > >  wrote:
>> > >
>> > > > Hey Konstantine,
>> > > >
>> > > > Thanks for the question. If these configs are not validated the
>> user's
>> > > > experience will be affected and upgrades from 3.0 will be harder.
>> > > >
>> > > > Best,
>> > > > Ryan Dielhenn
>> > > >
>> > > > On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
>> > > > kkaranta...@apache.org> wrote:
>> > > >
>> > > > > Thanks for reporting this issue Ryan.
>> > > > >
>> > > > > I believe what you mention corresponds to the ticket you created
>> here:
>> > > > > https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
>> > > > >
>> > > > > What happens if the configurations are present but the broker
>> doesn't
>> > > > fail
>> > > > > at startup when configured to run in KRaft mode?
>> > > > > Asking to see if we have any workarounds in our availability.
>> > > > >
>> > > > > Thanks,
>> > > > > Konstantine
>> > > > >
>> > > > > On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
>> > > > >  wrote:
>> > > > >
>> > > > > > Hi,
>> > > > > >
>> > > > > > Disregard log.clean.policy being included in this blocker.
>> > > > > >
>> > > > > > Best,
>> > > > > > Ryan Dielhenn
>> > > > > >
>> > > > > > On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn <
>> > > rdielh...@confluent.io>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Hey Konstantine,
>> > > > > > >
>> > > > > > > I'd like to report another bug in KRaft.
>> > > > > > >
>> > > > > > > log.cleanup.policy, alter.config.policy.class.name, and
>> > > > > > > create.topic.policy.class.name are all unsupported by KRaft
>> but
>> > > > KRaft
>> > > > > > > servers allow them to be configured. I believe this should be
>> > > > > considered
>> > > > > > a
>> > > > > > > blocker and that KRaft servers should fail startup if any of
>> these
>> > > > are
>> > > > > > > configured. I do not have a PR yet but will soon.
>> > > > > > >
>> > > > > > > On another note, I have a PR for the dynamic broker
>> configuration
>> > > fix
>> > > > > > > here: https://github.com/apache/kafka/pull/11141
>> > > > > > >
>> > > > > > > Best,
>> > > > > > > Ryan Dielhenn
>> > > > > > >
>> > > > > > > On Wed, May 26, 2021 at 2:48 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for reporting this new issue Ryan,

It's important and this issue seems to have clearly regressed dynamic
default configs in the 3.0 branch.
So, it's approved.

Konstantine


On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
 wrote:

> Hey all,
>
> For the KIP-500 work for 3.0 we would like to propose the following
> Jiras as blockers:
>
> 1. https://issues.apache.org/jira/browse/KAFKA-13168
> 2. https://issues.apache.org/jira/browse/KAFKA-13165
> 3. https://issues.apache.org/jira/browse/KAFKA-13161
>
> The description for each Jira should have more details.
>
> Thanks,
> -Jose
>
> On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
>  wrote:
> >
> > Hi Konstantine,
> >
> > I would like to report another bug in KRaft.
> >
> > The ConfigHandler that processes dynamic broker config deltas in KRaft
> > expects that the default resource name for dynamic broker configs is the
> > old default entity name used in ZK: "". Since dynamic default
> > broker configs are persisted as empty string in the quorum instead of
> > "", the brokers are not updating the their default configuration
> > when they see empty string as a resource name in the config delta and are
> > throwing a NumberFormatException when they try to parse the resource name
> > to process it as a per-broker configuration.
> >
> > I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160
> >
> > I also have a PR to fix this: https://github.com/apache/kafka/pull/11168
> >
> > I think that this should be a blocker for 3.0 because dynamic default
> > broker configs will not be usable in KRaft otherwise.
> >
> > Best,
> > Ryan Dielhenn
> >
> > On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
> > kkaranta...@apache.org> wrote:
> >
> > > Thanks Ryan,
> > >
> > > Approved. Seems also like a low risk fix.
> > > With that opportunity, let's make sure there are no other configs that
> > > would need a similar validation.
> > >
> > > Konstantine
> > >
> > > On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
> > >  wrote:
> > >
> > > > Hey Konstantine,
> > > >
> > > > Thanks for the question. If these configs are not validated the
> user's
> > > > experience will be affected and upgrades from 3.0 will be harder.
> > > >
> > > > Best,
> > > > Ryan Dielhenn
> > > >
> > > > On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
> > > > kkaranta...@apache.org> wrote:
> > > >
> > > > > Thanks for reporting this issue Ryan.
> > > > >
> > > > > I believe what you mention corresponds to the ticket you created
> here:
> > > > > https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
> > > > >
> > > > > What happens if the configurations are present but the broker
> doesn't
> > > > fail
> > > > > at startup when configured to run in KRaft mode?
> > > > > Asking to see if we have any workarounds in our availability.
> > > > >
> > > > > Thanks,
> > > > > Konstantine
> > > > >
> > > > > On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
> > > > >  wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Disregard log.clean.policy being included in this blocker.
> > > > > >
> > > > > > Best,
> > > > > > Ryan Dielhenn
> > > > > >
> > > > > > On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn <
> > > rdielh...@confluent.io>
> > > > > > wrote:
> > > > > >
> > > > > > > Hey Konstantine,
> > > > > > >
> > > > > > > I'd like to report another bug in KRaft.
> > > > > > >
> > > > > > > log.cleanup.policy, alter.config.policy.class.name, and
> > > > > > > create.topic.policy.class.name are all unsupported by KRaft
> but
> > > > KRaft
> > > > > > > servers allow them to be configured. I believe this should be
> > > > > considered
> > > > > > a
> > > > > > > blocker and that KRaft servers should fail startup if any of
> these
> > > > are
> > > > > > > configured. I do not have a PR yet but will soon.
> > > > > > >
> > > > > > > On another note, I have a PR for the dynamic broker
> configuration
> > > fix
> > > > > > > here: https://github.com/apache/kafka/pull/11141
> > > > > > >
> > > > > > > Best,
> > > > > > > Ryan Dielhenn
> > > > > > >
> > > > > > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> > > > > > >  wrote:
> > > > > > >
> > > > > > >> Hi all,
> > > > > > >>
> > > > > > >> Please find below the updated release plan for the Apache
> Kafka
> > > > 3.0.0
> > > > > > >> release.
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > > > > > >>
> > > > > > >> New suggested dates for the release are as follows:
> > > > > > >>
> > > > > > >> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > > > > > >> Feature Freeze is 30 June 2021 (new date, extended by two
> weeks)
> > > > > > >> Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > > > > > >>
> > > > > > >> At least two weeks of stabilization will follow Code Freeze.
> > > > > > >>
> > > > > > >> The release plan is up to date and currently includes all the
> > > > approved
> > > 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[José Armando García Sancio]

Hey all,

For the KIP-500 work for 3.0 we would like to propose the following
Jiras as blockers:

1. https://issues.apache.org/jira/browse/KAFKA-13168
2. https://issues.apache.org/jira/browse/KAFKA-13165
3. https://issues.apache.org/jira/browse/KAFKA-13161

The description for each Jira should have more details.

Thanks,
-Jose

On Tue, Aug 3, 2021 at 12:14 PM Ryan Dielhenn
 wrote:
>
> Hi Konstantine,
>
> I would like to report another bug in KRaft.
>
> The ConfigHandler that processes dynamic broker config deltas in KRaft
> expects that the default resource name for dynamic broker configs is the
> old default entity name used in ZK: "". Since dynamic default
> broker configs are persisted as empty string in the quorum instead of
> "", the brokers are not updating the their default configuration
> when they see empty string as a resource name in the config delta and are
> throwing a NumberFormatException when they try to parse the resource name
> to process it as a per-broker configuration.
>
> I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160
>
> I also have a PR to fix this: https://github.com/apache/kafka/pull/11168
>
> I think that this should be a blocker for 3.0 because dynamic default
> broker configs will not be usable in KRaft otherwise.
>
> Best,
> Ryan Dielhenn
>
> On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
> kkaranta...@apache.org> wrote:
>
> > Thanks Ryan,
> >
> > Approved. Seems also like a low risk fix.
> > With that opportunity, let's make sure there are no other configs that
> > would need a similar validation.
> >
> > Konstantine
> >
> > On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
> >  wrote:
> >
> > > Hey Konstantine,
> > >
> > > Thanks for the question. If these configs are not validated the user's
> > > experience will be affected and upgrades from 3.0 will be harder.
> > >
> > > Best,
> > > Ryan Dielhenn
> > >
> > > On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
> > > kkaranta...@apache.org> wrote:
> > >
> > > > Thanks for reporting this issue Ryan.
> > > >
> > > > I believe what you mention corresponds to the ticket you created here:
> > > > https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
> > > >
> > > > What happens if the configurations are present but the broker doesn't
> > > fail
> > > > at startup when configured to run in KRaft mode?
> > > > Asking to see if we have any workarounds in our availability.
> > > >
> > > > Thanks,
> > > > Konstantine
> > > >
> > > > On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
> > > >  wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Disregard log.clean.policy being included in this blocker.
> > > > >
> > > > > Best,
> > > > > Ryan Dielhenn
> > > > >
> > > > > On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn <
> > rdielh...@confluent.io>
> > > > > wrote:
> > > > >
> > > > > > Hey Konstantine,
> > > > > >
> > > > > > I'd like to report another bug in KRaft.
> > > > > >
> > > > > > log.cleanup.policy, alter.config.policy.class.name, and
> > > > > > create.topic.policy.class.name are all unsupported by KRaft but
> > > KRaft
> > > > > > servers allow them to be configured. I believe this should be
> > > > considered
> > > > > a
> > > > > > blocker and that KRaft servers should fail startup if any of these
> > > are
> > > > > > configured. I do not have a PR yet but will soon.
> > > > > >
> > > > > > On another note, I have a PR for the dynamic broker configuration
> > fix
> > > > > > here: https://github.com/apache/kafka/pull/11141
> > > > > >
> > > > > > Best,
> > > > > > Ryan Dielhenn
> > > > > >
> > > > > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> > > > > >  wrote:
> > > > > >
> > > > > >> Hi all,
> > > > > >>
> > > > > >> Please find below the updated release plan for the Apache Kafka
> > > 3.0.0
> > > > > >> release.
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > > > > >>
> > > > > >> New suggested dates for the release are as follows:
> > > > > >>
> > > > > >> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > > > > >> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > > > > >> Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > > > > >>
> > > > > >> At least two weeks of stabilization will follow Code Freeze.
> > > > > >>
> > > > > >> The release plan is up to date and currently includes all the
> > > approved
> > > > > >> KIPs
> > > > > >> that are targeting 3.0.0.
> > > > > >>
> > > > > >> Please let me know if you have any objections with the recent
> > > > extension
> > > > > of
> > > > > >> Feature Freeze and Code Freeze or any other concerns.
> > > > > >>
> > > > > >> Regards,
> > > > > >> Konstantine
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >



-- 
-Jose

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ryan Dielhenn]

Hi Konstantine,

I would like to report another bug in KRaft.

The ConfigHandler that processes dynamic broker config deltas in KRaft
expects that the default resource name for dynamic broker configs is the
old default entity name used in ZK: "". Since dynamic default
broker configs are persisted as empty string in the quorum instead of
"", the brokers are not updating the their default configuration
when they see empty string as a resource name in the config delta and are
throwing a NumberFormatException when they try to parse the resource name
to process it as a per-broker configuration.

I filed a JIRA: https://issues.apache.org/jira/browse/KAFKA-13160

I also have a PR to fix this: https://github.com/apache/kafka/pull/11168

I think that this should be a blocker for 3.0 because dynamic default
broker configs will not be usable in KRaft otherwise.

Best,
Ryan Dielhenn

On Sat, Jul 31, 2021 at 10:42 AM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

> Thanks Ryan,
>
> Approved. Seems also like a low risk fix.
> With that opportunity, let's make sure there are no other configs that
> would need a similar validation.
>
> Konstantine
>
> On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
>  wrote:
>
> > Hey Konstantine,
> >
> > Thanks for the question. If these configs are not validated the user's
> > experience will be affected and upgrades from 3.0 will be harder.
> >
> > Best,
> > Ryan Dielhenn
> >
> > On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
> > kkaranta...@apache.org> wrote:
> >
> > > Thanks for reporting this issue Ryan.
> > >
> > > I believe what you mention corresponds to the ticket you created here:
> > > https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
> > >
> > > What happens if the configurations are present but the broker doesn't
> > fail
> > > at startup when configured to run in KRaft mode?
> > > Asking to see if we have any workarounds in our availability.
> > >
> > > Thanks,
> > > Konstantine
> > >
> > > On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
> > >  wrote:
> > >
> > > > Hi,
> > > >
> > > > Disregard log.clean.policy being included in this blocker.
> > > >
> > > > Best,
> > > > Ryan Dielhenn
> > > >
> > > > On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn <
> rdielh...@confluent.io>
> > > > wrote:
> > > >
> > > > > Hey Konstantine,
> > > > >
> > > > > I'd like to report another bug in KRaft.
> > > > >
> > > > > log.cleanup.policy, alter.config.policy.class.name, and
> > > > > create.topic.policy.class.name are all unsupported by KRaft but
> > KRaft
> > > > > servers allow them to be configured. I believe this should be
> > > considered
> > > > a
> > > > > blocker and that KRaft servers should fail startup if any of these
> > are
> > > > > configured. I do not have a PR yet but will soon.
> > > > >
> > > > > On another note, I have a PR for the dynamic broker configuration
> fix
> > > > > here: https://github.com/apache/kafka/pull/11141
> > > > >
> > > > > Best,
> > > > > Ryan Dielhenn
> > > > >
> > > > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> > > > >  wrote:
> > > > >
> > > > >> Hi all,
> > > > >>
> > > > >> Please find below the updated release plan for the Apache Kafka
> > 3.0.0
> > > > >> release.
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > > > >>
> > > > >> New suggested dates for the release are as follows:
> > > > >>
> > > > >> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > > > >> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > > > >> Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > > > >>
> > > > >> At least two weeks of stabilization will follow Code Freeze.
> > > > >>
> > > > >> The release plan is up to date and currently includes all the
> > approved
> > > > >> KIPs
> > > > >> that are targeting 3.0.0.
> > > > >>
> > > > >> Please let me know if you have any objections with the recent
> > > extension
> > > > of
> > > > >> Feature Freeze and Code Freeze or any other concerns.
> > > > >>
> > > > >> Regards,
> > > > >> Konstantine
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks Ryan,

Approved. Seems also like a low risk fix.
With that opportunity, let's make sure there are no other configs that
would need a similar validation.

Konstantine

On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
 wrote:

> Hey Konstantine,
>
> Thanks for the question. If these configs are not validated the user's
> experience will be affected and upgrades from 3.0 will be harder.
>
> Best,
> Ryan Dielhenn
>
> On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
> kkaranta...@apache.org> wrote:
>
> > Thanks for reporting this issue Ryan.
> >
> > I believe what you mention corresponds to the ticket you created here:
> > https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
> >
> > What happens if the configurations are present but the broker doesn't
> fail
> > at startup when configured to run in KRaft mode?
> > Asking to see if we have any workarounds in our availability.
> >
> > Thanks,
> > Konstantine
> >
> > On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
> >  wrote:
> >
> > > Hi,
> > >
> > > Disregard log.clean.policy being included in this blocker.
> > >
> > > Best,
> > > Ryan Dielhenn
> > >
> > > On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn 
> > > wrote:
> > >
> > > > Hey Konstantine,
> > > >
> > > > I'd like to report another bug in KRaft.
> > > >
> > > > log.cleanup.policy, alter.config.policy.class.name, and
> > > > create.topic.policy.class.name are all unsupported by KRaft but
> KRaft
> > > > servers allow them to be configured. I believe this should be
> > considered
> > > a
> > > > blocker and that KRaft servers should fail startup if any of these
> are
> > > > configured. I do not have a PR yet but will soon.
> > > >
> > > > On another note, I have a PR for the dynamic broker configuration fix
> > > > here: https://github.com/apache/kafka/pull/11141
> > > >
> > > > Best,
> > > > Ryan Dielhenn
> > > >
> > > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> > > >  wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> Please find below the updated release plan for the Apache Kafka
> 3.0.0
> > > >> release.
> > > >>
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > > >>
> > > >> New suggested dates for the release are as follows:
> > > >>
> > > >> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > > >> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > > >> Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > > >>
> > > >> At least two weeks of stabilization will follow Code Freeze.
> > > >>
> > > >> The release plan is up to date and currently includes all the
> approved
> > > >> KIPs
> > > >> that are targeting 3.0.0.
> > > >>
> > > >> Please let me know if you have any objections with the recent
> > extension
> > > of
> > > >> Feature Freeze and Code Freeze or any other concerns.
> > > >>
> > > >> Regards,
> > > >> Konstantine
> > > >>
> > > >
> > >
> >
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ryan Dielhenn]

Hey Konstantine,

Thanks for the question. If these configs are not validated the user's
experience will be affected and upgrades from 3.0 will be harder.

Best,
Ryan Dielhenn

On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

> Thanks for reporting this issue Ryan.
>
> I believe what you mention corresponds to the ticket you created here:
> https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
>
> What happens if the configurations are present but the broker doesn't fail
> at startup when configured to run in KRaft mode?
> Asking to see if we have any workarounds in our availability.
>
> Thanks,
> Konstantine
>
> On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
>  wrote:
>
> > Hi,
> >
> > Disregard log.clean.policy being included in this blocker.
> >
> > Best,
> > Ryan Dielhenn
> >
> > On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn 
> > wrote:
> >
> > > Hey Konstantine,
> > >
> > > I'd like to report another bug in KRaft.
> > >
> > > log.cleanup.policy, alter.config.policy.class.name, and
> > > create.topic.policy.class.name are all unsupported by KRaft but KRaft
> > > servers allow them to be configured. I believe this should be
> considered
> > a
> > > blocker and that KRaft servers should fail startup if any of these are
> > > configured. I do not have a PR yet but will soon.
> > >
> > > On another note, I have a PR for the dynamic broker configuration fix
> > > here: https://github.com/apache/kafka/pull/11141
> > >
> > > Best,
> > > Ryan Dielhenn
> > >
> > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> > >  wrote:
> > >
> > >> Hi all,
> > >>
> > >> Please find below the updated release plan for the Apache Kafka 3.0.0
> > >> release.
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > >>
> > >> New suggested dates for the release are as follows:
> > >>
> > >> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > >> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > >> Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > >>
> > >> At least two weeks of stabilization will follow Code Freeze.
> > >>
> > >> The release plan is up to date and currently includes all the approved
> > >> KIPs
> > >> that are targeting 3.0.0.
> > >>
> > >> Please let me know if you have any objections with the recent
> extension
> > of
> > >> Feature Freeze and Code Freeze or any other concerns.
> > >>
> > >> Regards,
> > >> Konstantine
> > >>
> > >
> >
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for reporting this issue Ryan.

I believe what you mention corresponds to the ticket you created here:
https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151

What happens if the configurations are present but the broker doesn't fail
at startup when configured to run in KRaft mode?
Asking to see if we have any workarounds in our availability.

Thanks,
Konstantine

On Thu, Jul 29, 2021 at 2:51 PM Ryan Dielhenn
 wrote:

> Hi,
>
> Disregard log.clean.policy being included in this blocker.
>
> Best,
> Ryan Dielhenn
>
> On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn 
> wrote:
>
> > Hey Konstantine,
> >
> > I'd like to report another bug in KRaft.
> >
> > log.cleanup.policy, alter.config.policy.class.name, and
> > create.topic.policy.class.name are all unsupported by KRaft but KRaft
> > servers allow them to be configured. I believe this should be considered
> a
> > blocker and that KRaft servers should fail startup if any of these are
> > configured. I do not have a PR yet but will soon.
> >
> > On another note, I have a PR for the dynamic broker configuration fix
> > here: https://github.com/apache/kafka/pull/11141
> >
> > Best,
> > Ryan Dielhenn
> >
> > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> >  wrote:
> >
> >> Hi all,
> >>
> >> Please find below the updated release plan for the Apache Kafka 3.0.0
> >> release.
> >>
> >>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> >>
> >> New suggested dates for the release are as follows:
> >>
> >> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> >> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> >> Code Freeze is 14 July 2021 (new date, extended by two weeks)
> >>
> >> At least two weeks of stabilization will follow Code Freeze.
> >>
> >> The release plan is up to date and currently includes all the approved
> >> KIPs
> >> that are targeting 3.0.0.
> >>
> >> Please let me know if you have any objections with the recent extension
> of
> >> Feature Freeze and Code Freeze or any other concerns.
> >>
> >> Regards,
> >> Konstantine
> >>
> >
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ryan Dielhenn]

Hi,

Disregard log.clean.policy being included in this blocker.

Best,
Ryan Dielhenn

On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn 
wrote:

> Hey Konstantine,
>
> I'd like to report another bug in KRaft.
>
> log.cleanup.policy, alter.config.policy.class.name, and
> create.topic.policy.class.name are all unsupported by KRaft but KRaft
> servers allow them to be configured. I believe this should be considered a
> blocker and that KRaft servers should fail startup if any of these are
> configured. I do not have a PR yet but will soon.
>
> On another note, I have a PR for the dynamic broker configuration fix
> here: https://github.com/apache/kafka/pull/11141
>
> Best,
> Ryan Dielhenn
>
> On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
>  wrote:
>
>> Hi all,
>>
>> Please find below the updated release plan for the Apache Kafka 3.0.0
>> release.
>>
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>>
>> New suggested dates for the release are as follows:
>>
>> KIP Freeze is 09 June 2021 (same date as in the initial plan)
>> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
>> Code Freeze is 14 July 2021 (new date, extended by two weeks)
>>
>> At least two weeks of stabilization will follow Code Freeze.
>>
>> The release plan is up to date and currently includes all the approved
>> KIPs
>> that are targeting 3.0.0.
>>
>> Please let me know if you have any objections with the recent extension of
>> Feature Freeze and Code Freeze or any other concerns.
>>
>> Regards,
>> Konstantine
>>
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ryan Dielhenn]

Hey Konstantine,

I'd like to report another bug in KRaft.

log.cleanup.policy, alter.config.policy.class.name, and
create.topic.policy.class.name are all unsupported by KRaft but KRaft
servers allow them to be configured. I believe this should be considered a
blocker and that KRaft servers should fail startup if any of these are
configured. I do not have a PR yet but will soon.

On another note, I have a PR for the dynamic broker configuration fix here:
https://github.com/apache/kafka/pull/11141

Best,
Ryan Dielhenn

On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
 wrote:

> Hi all,
>
> Please find below the updated release plan for the Apache Kafka 3.0.0
> release.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>
> New suggested dates for the release are as follows:
>
> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> Code Freeze is 14 July 2021 (new date, extended by two weeks)
>
> At least two weeks of stabilization will follow Code Freeze.
>
> The release plan is up to date and currently includes all the approved KIPs
> that are targeting 3.0.0.
>
> Please let me know if you have any objections with the recent extension of
> Feature Freeze and Code Freeze or any other concerns.
>
> Regards,
> Konstantine
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks Ryan and Ron for reporting these new issues.

KAFKA-13142 is approved as an issue with no good workaround (and keeping in
mind that we have a few open blockers still) and
KAFKA-13137 is approved as a blocker because it's a regression.

Konstantine




On Tue, Jul 27, 2021 at 5:22 PM Ron Dagostino  wrote:

> Hi Konstantine. I've opened KAFKA-13137 as a potential blocker.  An
> approved PR is available at
> https://github.com/apache/kafka/pull/11131.  The kafka.controller
> metrics that the KRaft controllers expose have the wrong MBean names.
>
> Ron
>
> > On Jul 27, 2021, at 8:13 PM, Ryan Dielhenn 
> wrote:
> >
> > Hello,
>
> >
> > I would like to report a bug in KRaft.
> >
> > Dynamic broker configs are not being validated on the brokers before
> being
> > forwarded to the controller and persisted in the metadata quorum. This
> is a
> > blocker because a core requirement of KRaft mode in 3.0 is that it should
> > support upgrades from 3.0. If invalid dynamic configs are persisted to
> > metadata then they will still be there after an upgrade.
> >
> > I believe that this should be considered as a blocker for 3.0 here is the
> > JIRA: https://issues.apache.org/jira/browse/KAFKA-13142. I will be
> working
> > on a PR this week.
> >
> > Best Regards,
> > Ryan
> >
> >> On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> >>  wrote:
> >>
> >> Hi all,
> >>
> >> Please find below the updated release plan for the Apache Kafka 3.0.0
> >> release.
> >>
> >>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> >>
> >> New suggested dates for the release are as follows:
> >>
> >> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> >> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> >> Code Freeze is 14 July 2021 (new date, extended by two weeks)
> >>
> >> At least two weeks of stabilization will follow Code Freeze.
> >>
> >> The release plan is up to date and currently includes all the approved
> KIPs
> >> that are targeting 3.0.0.
> >>
> >> Please let me know if you have any objections with the recent extension
> of
> >> Feature Freeze and Code Freeze or any other concerns.
> >>
> >> Regards,
> >> Konstantine
> >>
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ron Dagostino]

Hi Konstantine. I've opened KAFKA-13137 as a potential blocker.  An
approved PR is available at
https://github.com/apache/kafka/pull/11131.  The kafka.controller
metrics that the KRaft controllers expose have the wrong MBean names.

Ron

> On Jul 27, 2021, at 8:13 PM, Ryan Dielhenn  
> wrote:
>
> Hello,

>
> I would like to report a bug in KRaft.
>
> Dynamic broker configs are not being validated on the brokers before being
> forwarded to the controller and persisted in the metadata quorum. This is a
> blocker because a core requirement of KRaft mode in 3.0 is that it should
> support upgrades from 3.0. If invalid dynamic configs are persisted to
> metadata then they will still be there after an upgrade.
>
> I believe that this should be considered as a blocker for 3.0 here is the
> JIRA: https://issues.apache.org/jira/browse/KAFKA-13142. I will be working
> on a PR this week.
>
> Best Regards,
> Ryan
>
>> On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
>>  wrote:
>>
>> Hi all,
>>
>> Please find below the updated release plan for the Apache Kafka 3.0.0
>> release.
>>
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>>
>> New suggested dates for the release are as follows:
>>
>> KIP Freeze is 09 June 2021 (same date as in the initial plan)
>> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
>> Code Freeze is 14 July 2021 (new date, extended by two weeks)
>>
>> At least two weeks of stabilization will follow Code Freeze.
>>
>> The release plan is up to date and currently includes all the approved KIPs
>> that are targeting 3.0.0.
>>
>> Please let me know if you have any objections with the recent extension of
>> Feature Freeze and Code Freeze or any other concerns.
>>
>> Regards,
>> Konstantine
>>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ryan Dielhenn]

Hello,

I would like to report a bug in KRaft.

Dynamic broker configs are not being validated on the brokers before being
forwarded to the controller and persisted in the metadata quorum. This is a
blocker because a core requirement of KRaft mode in 3.0 is that it should
support upgrades from 3.0. If invalid dynamic configs are persisted to
metadata then they will still be there after an upgrade.

I believe that this should be considered as a blocker for 3.0 here is the
JIRA: https://issues.apache.org/jira/browse/KAFKA-13142. I will be working
on a PR this week.

Best Regards,
Ryan

On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
 wrote:

> Hi all,
>
> Please find below the updated release plan for the Apache Kafka 3.0.0
> release.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>
> New suggested dates for the release are as follows:
>
> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> Code Freeze is 14 July 2021 (new date, extended by two weeks)
>
> At least two weeks of stabilization will follow Code Freeze.
>
> The release plan is up to date and currently includes all the approved KIPs
> that are targeting 3.0.0.
>
> Please let me know if you have any objections with the recent extension of
> Feature Freeze and Code Freeze or any other concerns.
>
> Regards,
> Konstantine
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi all,

I'd like to report a bug for Connect this time.

System test runs revealed an issue when restarting a connector but not the
tasks.
You may find a description in:
https://issues.apache.org/jira/browse/KAFKA-13139
The underlying issue is related to the implementation of KIP-745.

This makes it a regression for 3.0 and given that it doesn't seem to have a
viable workaround other than not using this specific functionality, I'm
willing to consider it as a blocker for 3.0.0 if there are no objections.
A PR is up for review: https://github.com/apache/kafka/pull/11132

Regards,
Konstantine

On Mon, Jul 26, 2021 at 9:15 AM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

>
> Hi Justine,
>
> Thanks for reporting this issue. Sounds like a regression in 3.0.
> Therefore, it would make sense to try to address it before we release
> 3.0.0.
>
> I marked the jira issue as a Blocker targeting 3.0. Hopefully your PR will
> fix the issue but let me know if we need to make further adjustments.
>
> Konstantine
>
>
> On Sun, Jul 25, 2021 at 7:55 PM Justine Olshan
>  wrote:
>
>> Hi Konstantine,
>> I've discovered a bug with topic IDs that can be encountered when
>> upgrading
>> from IBP versions below 2.8.
>>
>> Since 2.8, when handling leader and isr requests, the request topic IDs
>> are
>> compared to the log IDs and partitions with inconsistent IDs are skipped.
>>
>> With a change introduced in 3.0, in some upgrade scenarios, topic IDs for
>> existing topics will not be assigned to the logs. For topics affected with
>> the issue, we will not be able to check the topic ID. We could potentially
>> handle partitions with inconsistent topic IDs incorrectly.
>>
>> I believe this should be considered a blocker for 3.0. JIRA is here
>>  and PR to fix the
>> issue
>> here .
>>
>> Thanks,
>> Justine
>>
>> On Fri, Jul 23, 2021 at 10:51 AM Konstantine Karantasis <
>> kkaranta...@apache.org> wrote:
>>
>> > Thanks for the PR and the follow up Sophie.
>> >
>> > We can still get this in and there's no risk to do so, given the
>> proposed
>> > changes.
>> > Therefore, I agree to cherry-pick to 3.0 since the PR is about to get
>> > merged.
>> >
>> > Konstantine
>> >
>> > On Thu, Jul 22, 2021 at 9:12 PM Sophie Blee-Goldman
>> >  wrote:
>> >
>> > > Hey Konstantine,
>> > >
>> > > A javadocs ticket of ours was demoted to a non-blocker earlier this
>> week
>> > > due to lack of action,
>> > > but I now have a PR ready and under review. It's picking up some
>> > essential
>> > > followup that was
>> > > missed during the implementation of KIP-633 and is pretty essential. I
>> > > tagged you on the PR,
>> > > it's technically touching on a few things that aren't just docs, but
>> only
>> > > to add a handful of checks
>> > > that already existed on the old APIs and just got missed on the new
>> APIs.
>> > > Anything beyond that
>> > > I left as a TODO to follow up on after 3.0.
>> > >
>> > > KAFKA-13021  ---
>> > > https://github.com/apache/kafka/pull/4
>> > >
>> > > I think we should be able to get it merged by tomorrow. Assuming we
>> do,
>> > can
>> > > I promote it back
>> > > to blocker status and pick the fix to the 3.0 branch?
>> > >
>> > > Thanks!
>> > > Sophie
>> > >
>> > > On Thu, Jul 22, 2021 at 4:29 PM Konstantine Karantasis
>> > >  wrote:
>> > >
>> > > > Thanks for raising this John.
>> > > >
>> > > > While we are working to eliminate the existing blockers I think it
>> > would
>> > > be
>> > > > great to use this time in order to test the upgrade path that you
>> > > mention.
>> > > >
>> > > > Before we approve a release candidate (once such a RC is generated)
>> we
>> > > > should confirm that the upgrade works as expected.
>> > > > So, I agree with you that this is not an RC generation blocker per
>> se
>> > but
>> > > > it's a release blocker overall.
>> > > >
>> > > > Konstantine
>> > > >
>> > > >
>> > > > On Thu, Jul 22, 2021 at 4:21 PM John Roesler 
>> > > wrote:
>> > > >
>> > > > > Hello Konstantine,
>> > > > >
>> > > > > Someone just called to my attention that KAFKA-12724 had not
>> > > > > been marked as a 3.0 blocker. We never added 2.8 to the
>> > > > > Streams upgrade system test suite. This isn't a blocker in
>> > > > > that it is a problem, but we should make sure that Streams
>> > > > > is actually upgradable before releasing 3.0.
>> > > > >
>> > > > > I'm sorry for the oversight. For what it's worth, I think we
>> > > > > could proceed with a release candidate while we continue to
>> > > > > address the missing system test.
>> > > > >
>> > > > > Thanks,
>> > > > > -John
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/KAFKA-12724
>> > > > >
>> > > > > On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
>> > > > > wrote:
>> > > > > > Thanks for the heads up Colin.
>> > > > > >
>> > > > > > KAFKA-13112 seems important and of course 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi Justine,

Thanks for reporting this issue. Sounds like a regression in 3.0.
Therefore, it would make sense to try to address it before we release
3.0.0.

I marked the jira issue as a Blocker targeting 3.0. Hopefully your PR will
fix the issue but let me know if we need to make further adjustments.

Konstantine


On Sun, Jul 25, 2021 at 7:55 PM Justine Olshan 
wrote:

> Hi Konstantine,
> I've discovered a bug with topic IDs that can be encountered when upgrading
> from IBP versions below 2.8.
>
> Since 2.8, when handling leader and isr requests, the request topic IDs are
> compared to the log IDs and partitions with inconsistent IDs are skipped.
>
> With a change introduced in 3.0, in some upgrade scenarios, topic IDs for
> existing topics will not be assigned to the logs. For topics affected with
> the issue, we will not be able to check the topic ID. We could potentially
> handle partitions with inconsistent topic IDs incorrectly.
>
> I believe this should be considered a blocker for 3.0. JIRA is here
>  and PR to fix the
> issue
> here .
>
> Thanks,
> Justine
>
> On Fri, Jul 23, 2021 at 10:51 AM Konstantine Karantasis <
> kkaranta...@apache.org> wrote:
>
> > Thanks for the PR and the follow up Sophie.
> >
> > We can still get this in and there's no risk to do so, given the proposed
> > changes.
> > Therefore, I agree to cherry-pick to 3.0 since the PR is about to get
> > merged.
> >
> > Konstantine
> >
> > On Thu, Jul 22, 2021 at 9:12 PM Sophie Blee-Goldman
> >  wrote:
> >
> > > Hey Konstantine,
> > >
> > > A javadocs ticket of ours was demoted to a non-blocker earlier this
> week
> > > due to lack of action,
> > > but I now have a PR ready and under review. It's picking up some
> > essential
> > > followup that was
> > > missed during the implementation of KIP-633 and is pretty essential. I
> > > tagged you on the PR,
> > > it's technically touching on a few things that aren't just docs, but
> only
> > > to add a handful of checks
> > > that already existed on the old APIs and just got missed on the new
> APIs.
> > > Anything beyond that
> > > I left as a TODO to follow up on after 3.0.
> > >
> > > KAFKA-13021  ---
> > > https://github.com/apache/kafka/pull/4
> > >
> > > I think we should be able to get it merged by tomorrow. Assuming we do,
> > can
> > > I promote it back
> > > to blocker status and pick the fix to the 3.0 branch?
> > >
> > > Thanks!
> > > Sophie
> > >
> > > On Thu, Jul 22, 2021 at 4:29 PM Konstantine Karantasis
> > >  wrote:
> > >
> > > > Thanks for raising this John.
> > > >
> > > > While we are working to eliminate the existing blockers I think it
> > would
> > > be
> > > > great to use this time in order to test the upgrade path that you
> > > mention.
> > > >
> > > > Before we approve a release candidate (once such a RC is generated)
> we
> > > > should confirm that the upgrade works as expected.
> > > > So, I agree with you that this is not an RC generation blocker per se
> > but
> > > > it's a release blocker overall.
> > > >
> > > > Konstantine
> > > >
> > > >
> > > > On Thu, Jul 22, 2021 at 4:21 PM John Roesler 
> > > wrote:
> > > >
> > > > > Hello Konstantine,
> > > > >
> > > > > Someone just called to my attention that KAFKA-12724 had not
> > > > > been marked as a 3.0 blocker. We never added 2.8 to the
> > > > > Streams upgrade system test suite. This isn't a blocker in
> > > > > that it is a problem, but we should make sure that Streams
> > > > > is actually upgradable before releasing 3.0.
> > > > >
> > > > > I'm sorry for the oversight. For what it's worth, I think we
> > > > > could proceed with a release candidate while we continue to
> > > > > address the missing system test.
> > > > >
> > > > > Thanks,
> > > > > -John
> > > > >
> > > > > https://issues.apache.org/jira/browse/KAFKA-12724
> > > > >
> > > > > On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
> > > > > wrote:
> > > > > > Thanks for the heads up Colin.
> > > > > >
> > > > > > KAFKA-13112 seems important and of course relevant to what we
> ship
> > > with
> > > > > > 3.0.
> > > > > > Same for the test failures captured by KAFKA-13095 and
> KAFKA-12851.
> > > > > Fixing
> > > > > > those will increase the stability of our builds.
> > > > > >
> > > > > > Therefore, considering these tickets as blockers currently makes
> > > sense
> > > > to
> > > > > > me.
> > > > > >
> > > > > > Konstantine
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe <
> cmcc...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > Hi Konstantine,
> > > > > > >
> > > > > > > Thanks for your work on this release! We discovered three
> blocker
> > > > bugs
> > > > > > > which are worth bringing up here:
> > > > > > >
> > > > > > > 1. KAFKA-13112: Controller's committed offset get out of sync
> > with
> > > > raft
> > > > > > > client listener 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Justine Olshan]

Hi Konstantine,
I've discovered a bug with topic IDs that can be encountered when upgrading
from IBP versions below 2.8.

Since 2.8, when handling leader and isr requests, the request topic IDs are
compared to the log IDs and partitions with inconsistent IDs are skipped.

With a change introduced in 3.0, in some upgrade scenarios, topic IDs for
existing topics will not be assigned to the logs. For topics affected with
the issue, we will not be able to check the topic ID. We could potentially
handle partitions with inconsistent topic IDs incorrectly.

I believe this should be considered a blocker for 3.0. JIRA is here
 and PR to fix the issue
here .

Thanks,
Justine

On Fri, Jul 23, 2021 at 10:51 AM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

> Thanks for the PR and the follow up Sophie.
>
> We can still get this in and there's no risk to do so, given the proposed
> changes.
> Therefore, I agree to cherry-pick to 3.0 since the PR is about to get
> merged.
>
> Konstantine
>
> On Thu, Jul 22, 2021 at 9:12 PM Sophie Blee-Goldman
>  wrote:
>
> > Hey Konstantine,
> >
> > A javadocs ticket of ours was demoted to a non-blocker earlier this week
> > due to lack of action,
> > but I now have a PR ready and under review. It's picking up some
> essential
> > followup that was
> > missed during the implementation of KIP-633 and is pretty essential. I
> > tagged you on the PR,
> > it's technically touching on a few things that aren't just docs, but only
> > to add a handful of checks
> > that already existed on the old APIs and just got missed on the new APIs.
> > Anything beyond that
> > I left as a TODO to follow up on after 3.0.
> >
> > KAFKA-13021  ---
> > https://github.com/apache/kafka/pull/4
> >
> > I think we should be able to get it merged by tomorrow. Assuming we do,
> can
> > I promote it back
> > to blocker status and pick the fix to the 3.0 branch?
> >
> > Thanks!
> > Sophie
> >
> > On Thu, Jul 22, 2021 at 4:29 PM Konstantine Karantasis
> >  wrote:
> >
> > > Thanks for raising this John.
> > >
> > > While we are working to eliminate the existing blockers I think it
> would
> > be
> > > great to use this time in order to test the upgrade path that you
> > mention.
> > >
> > > Before we approve a release candidate (once such a RC is generated) we
> > > should confirm that the upgrade works as expected.
> > > So, I agree with you that this is not an RC generation blocker per se
> but
> > > it's a release blocker overall.
> > >
> > > Konstantine
> > >
> > >
> > > On Thu, Jul 22, 2021 at 4:21 PM John Roesler 
> > wrote:
> > >
> > > > Hello Konstantine,
> > > >
> > > > Someone just called to my attention that KAFKA-12724 had not
> > > > been marked as a 3.0 blocker. We never added 2.8 to the
> > > > Streams upgrade system test suite. This isn't a blocker in
> > > > that it is a problem, but we should make sure that Streams
> > > > is actually upgradable before releasing 3.0.
> > > >
> > > > I'm sorry for the oversight. For what it's worth, I think we
> > > > could proceed with a release candidate while we continue to
> > > > address the missing system test.
> > > >
> > > > Thanks,
> > > > -John
> > > >
> > > > https://issues.apache.org/jira/browse/KAFKA-12724
> > > >
> > > > On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
> > > > wrote:
> > > > > Thanks for the heads up Colin.
> > > > >
> > > > > KAFKA-13112 seems important and of course relevant to what we ship
> > with
> > > > > 3.0.
> > > > > Same for the test failures captured by KAFKA-13095 and KAFKA-12851.
> > > > Fixing
> > > > > those will increase the stability of our builds.
> > > > >
> > > > > Therefore, considering these tickets as blockers currently makes
> > sense
> > > to
> > > > > me.
> > > > >
> > > > > Konstantine
> > > > >
> > > > >
> > > > > On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe 
> > > > wrote:
> > > > >
> > > > > > Hi Konstantine,
> > > > > >
> > > > > > Thanks for your work on this release! We discovered three blocker
> > > bugs
> > > > > > which are worth bringing up here:
> > > > > >
> > > > > > 1. KAFKA-13112: Controller's committed offset get out of sync
> with
> > > raft
> > > > > > client listener context
> > > > > > 2. KAFKA-13095: TransactionsTest is failing in kraft mode
> > > > > > 3. KAFKA-12851: Flaky Test
> > > > > > RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable
> > > > > >
> > > > > > There are two subtasks for #1 which we are working on. We suspect
> > > that
> > > > #3
> > > > > > has been fixed by a previous fix we made... we're looking into
> it.
> > > > > >
> > > > > > best,
> > > > > > Colin
> > > > > >
> > > > > > On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Since last week, we have reached the stage of Code Freeze for
> the
> > > > 3.0.0
> > > > > > > Apache 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for the PR and the follow up Sophie.

We can still get this in and there's no risk to do so, given the proposed
changes.
Therefore, I agree to cherry-pick to 3.0 since the PR is about to get
merged.

Konstantine

On Thu, Jul 22, 2021 at 9:12 PM Sophie Blee-Goldman
 wrote:

> Hey Konstantine,
>
> A javadocs ticket of ours was demoted to a non-blocker earlier this week
> due to lack of action,
> but I now have a PR ready and under review. It's picking up some essential
> followup that was
> missed during the implementation of KIP-633 and is pretty essential. I
> tagged you on the PR,
> it's technically touching on a few things that aren't just docs, but only
> to add a handful of checks
> that already existed on the old APIs and just got missed on the new APIs.
> Anything beyond that
> I left as a TODO to follow up on after 3.0.
>
> KAFKA-13021  ---
> https://github.com/apache/kafka/pull/4
>
> I think we should be able to get it merged by tomorrow. Assuming we do, can
> I promote it back
> to blocker status and pick the fix to the 3.0 branch?
>
> Thanks!
> Sophie
>
> On Thu, Jul 22, 2021 at 4:29 PM Konstantine Karantasis
>  wrote:
>
> > Thanks for raising this John.
> >
> > While we are working to eliminate the existing blockers I think it would
> be
> > great to use this time in order to test the upgrade path that you
> mention.
> >
> > Before we approve a release candidate (once such a RC is generated) we
> > should confirm that the upgrade works as expected.
> > So, I agree with you that this is not an RC generation blocker per se but
> > it's a release blocker overall.
> >
> > Konstantine
> >
> >
> > On Thu, Jul 22, 2021 at 4:21 PM John Roesler 
> wrote:
> >
> > > Hello Konstantine,
> > >
> > > Someone just called to my attention that KAFKA-12724 had not
> > > been marked as a 3.0 blocker. We never added 2.8 to the
> > > Streams upgrade system test suite. This isn't a blocker in
> > > that it is a problem, but we should make sure that Streams
> > > is actually upgradable before releasing 3.0.
> > >
> > > I'm sorry for the oversight. For what it's worth, I think we
> > > could proceed with a release candidate while we continue to
> > > address the missing system test.
> > >
> > > Thanks,
> > > -John
> > >
> > > https://issues.apache.org/jira/browse/KAFKA-12724
> > >
> > > On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
> > > wrote:
> > > > Thanks for the heads up Colin.
> > > >
> > > > KAFKA-13112 seems important and of course relevant to what we ship
> with
> > > > 3.0.
> > > > Same for the test failures captured by KAFKA-13095 and KAFKA-12851.
> > > Fixing
> > > > those will increase the stability of our builds.
> > > >
> > > > Therefore, considering these tickets as blockers currently makes
> sense
> > to
> > > > me.
> > > >
> > > > Konstantine
> > > >
> > > >
> > > > On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe 
> > > wrote:
> > > >
> > > > > Hi Konstantine,
> > > > >
> > > > > Thanks for your work on this release! We discovered three blocker
> > bugs
> > > > > which are worth bringing up here:
> > > > >
> > > > > 1. KAFKA-13112: Controller's committed offset get out of sync with
> > raft
> > > > > client listener context
> > > > > 2. KAFKA-13095: TransactionsTest is failing in kraft mode
> > > > > 3. KAFKA-12851: Flaky Test
> > > > > RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable
> > > > >
> > > > > There are two subtasks for #1 which we are working on. We suspect
> > that
> > > #3
> > > > > has been fixed by a previous fix we made... we're looking into it.
> > > > >
> > > > > best,
> > > > > Colin
> > > > >
> > > > > On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > Since last week, we have reached the stage of Code Freeze for the
> > > 3.0.0
> > > > > > Apache Kafka release.
> > > > > >
> > > > > > From this point forward and until the official release of 3.0.0,
> > only
> > > > > > critical fixes for blocker issues should be merged to the 3.0
> > release
> > > > > > branch.
> > > > > >
> > > > > > The release plan currently includes ten (10) such known blockers.
> > > > > >
> > > > > >
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> > > > > >
> > > > > > Besides these issues, any new issue that potentially gets
> > discovered
> > > will
> > > > > > need to be reported on dev@kafka.apache.org (under this thread)
> > and
> > > be
> > > > > > evaluated as a release blocker. At this point, the bar for such
> > > issues is
> > > > > > high; they need to be regressions or critical issues without an
> > > > > acceptable
> > > > > > workaround to be considered as release blockers.
> > > > > >
> > > > > > Exceptions of changes that may be merged to the 3.0 branch
> without
> > a
> > > > > > mention on the dev mailing list are fixes for test failures that
> > will
> > > > > help
> > > > > > stabilize the build and small documentation 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Sophie Blee-Goldman]

Hey Konstantine,

A javadocs ticket of ours was demoted to a non-blocker earlier this week
due to lack of action,
but I now have a PR ready and under review. It's picking up some essential
followup that was
missed during the implementation of KIP-633 and is pretty essential. I
tagged you on the PR,
it's technically touching on a few things that aren't just docs, but only
to add a handful of checks
that already existed on the old APIs and just got missed on the new APIs.
Anything beyond that
I left as a TODO to follow up on after 3.0.

KAFKA-13021  ---
https://github.com/apache/kafka/pull/4

I think we should be able to get it merged by tomorrow. Assuming we do, can
I promote it back
to blocker status and pick the fix to the 3.0 branch?

Thanks!
Sophie

On Thu, Jul 22, 2021 at 4:29 PM Konstantine Karantasis
 wrote:

> Thanks for raising this John.
>
> While we are working to eliminate the existing blockers I think it would be
> great to use this time in order to test the upgrade path that you mention.
>
> Before we approve a release candidate (once such a RC is generated) we
> should confirm that the upgrade works as expected.
> So, I agree with you that this is not an RC generation blocker per se but
> it's a release blocker overall.
>
> Konstantine
>
>
> On Thu, Jul 22, 2021 at 4:21 PM John Roesler  wrote:
>
> > Hello Konstantine,
> >
> > Someone just called to my attention that KAFKA-12724 had not
> > been marked as a 3.0 blocker. We never added 2.8 to the
> > Streams upgrade system test suite. This isn't a blocker in
> > that it is a problem, but we should make sure that Streams
> > is actually upgradable before releasing 3.0.
> >
> > I'm sorry for the oversight. For what it's worth, I think we
> > could proceed with a release candidate while we continue to
> > address the missing system test.
> >
> > Thanks,
> > -John
> >
> > https://issues.apache.org/jira/browse/KAFKA-12724
> >
> > On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
> > wrote:
> > > Thanks for the heads up Colin.
> > >
> > > KAFKA-13112 seems important and of course relevant to what we ship with
> > > 3.0.
> > > Same for the test failures captured by KAFKA-13095 and KAFKA-12851.
> > Fixing
> > > those will increase the stability of our builds.
> > >
> > > Therefore, considering these tickets as blockers currently makes sense
> to
> > > me.
> > >
> > > Konstantine
> > >
> > >
> > > On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe 
> > wrote:
> > >
> > > > Hi Konstantine,
> > > >
> > > > Thanks for your work on this release! We discovered three blocker
> bugs
> > > > which are worth bringing up here:
> > > >
> > > > 1. KAFKA-13112: Controller's committed offset get out of sync with
> raft
> > > > client listener context
> > > > 2. KAFKA-13095: TransactionsTest is failing in kraft mode
> > > > 3. KAFKA-12851: Flaky Test
> > > > RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable
> > > >
> > > > There are two subtasks for #1 which we are working on. We suspect
> that
> > #3
> > > > has been fixed by a previous fix we made... we're looking into it.
> > > >
> > > > best,
> > > > Colin
> > > >
> > > > On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> > > > > Hi all,
> > > > >
> > > > > Since last week, we have reached the stage of Code Freeze for the
> > 3.0.0
> > > > > Apache Kafka release.
> > > > >
> > > > > From this point forward and until the official release of 3.0.0,
> only
> > > > > critical fixes for blocker issues should be merged to the 3.0
> release
> > > > > branch.
> > > > >
> > > > > The release plan currently includes ten (10) such known blockers.
> > > > >
> > > > >
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> > > > >
> > > > > Besides these issues, any new issue that potentially gets
> discovered
> > will
> > > > > need to be reported on dev@kafka.apache.org (under this thread)
> and
> > be
> > > > > evaluated as a release blocker. At this point, the bar for such
> > issues is
> > > > > high; they need to be regressions or critical issues without an
> > > > acceptable
> > > > > workaround to be considered as release blockers.
> > > > >
> > > > > Exceptions of changes that may be merged to the 3.0 branch without
> a
> > > > > mention on the dev mailing list are fixes for test failures that
> will
> > > > help
> > > > > stabilize the build and small documentation changes.
> > > > >
> > > > > If by the end of this week we are down to zero blockers and have
> > green
> > > > > builds and passing system tests, I will attempt to generate the
> first
> > > > > Release Candidate (RC) for 3.0.0 on Friday.
> > > > >
> > > > > Thank you all for the hard work so far.
> > > > > Konstantine
> > > > >
> > > > >
> > > > > On Mon, Jul 12, 2021 at 1:59 PM Konstantine Karantasis
> > > > >  wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > This is a reminder that Code Freeze for Apache Kafka 3.0 is
> coming
> > up
> > > > 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for raising this John.

While we are working to eliminate the existing blockers I think it would be
great to use this time in order to test the upgrade path that you mention.

Before we approve a release candidate (once such a RC is generated) we
should confirm that the upgrade works as expected.
So, I agree with you that this is not an RC generation blocker per se but
it's a release blocker overall.

Konstantine


On Thu, Jul 22, 2021 at 4:21 PM John Roesler  wrote:

> Hello Konstantine,
>
> Someone just called to my attention that KAFKA-12724 had not
> been marked as a 3.0 blocker. We never added 2.8 to the
> Streams upgrade system test suite. This isn't a blocker in
> that it is a problem, but we should make sure that Streams
> is actually upgradable before releasing 3.0.
>
> I'm sorry for the oversight. For what it's worth, I think we
> could proceed with a release candidate while we continue to
> address the missing system test.
>
> Thanks,
> -John
>
> https://issues.apache.org/jira/browse/KAFKA-12724
>
> On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
> wrote:
> > Thanks for the heads up Colin.
> >
> > KAFKA-13112 seems important and of course relevant to what we ship with
> > 3.0.
> > Same for the test failures captured by KAFKA-13095 and KAFKA-12851.
> Fixing
> > those will increase the stability of our builds.
> >
> > Therefore, considering these tickets as blockers currently makes sense to
> > me.
> >
> > Konstantine
> >
> >
> > On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe 
> wrote:
> >
> > > Hi Konstantine,
> > >
> > > Thanks for your work on this release! We discovered three blocker bugs
> > > which are worth bringing up here:
> > >
> > > 1. KAFKA-13112: Controller's committed offset get out of sync with raft
> > > client listener context
> > > 2. KAFKA-13095: TransactionsTest is failing in kraft mode
> > > 3. KAFKA-12851: Flaky Test
> > > RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable
> > >
> > > There are two subtasks for #1 which we are working on. We suspect that
> #3
> > > has been fixed by a previous fix we made... we're looking into it.
> > >
> > > best,
> > > Colin
> > >
> > > On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> > > > Hi all,
> > > >
> > > > Since last week, we have reached the stage of Code Freeze for the
> 3.0.0
> > > > Apache Kafka release.
> > > >
> > > > From this point forward and until the official release of 3.0.0, only
> > > > critical fixes for blocker issues should be merged to the 3.0 release
> > > > branch.
> > > >
> > > > The release plan currently includes ten (10) such known blockers.
> > > >
> > > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> > > >
> > > > Besides these issues, any new issue that potentially gets discovered
> will
> > > > need to be reported on dev@kafka.apache.org (under this thread) and
> be
> > > > evaluated as a release blocker. At this point, the bar for such
> issues is
> > > > high; they need to be regressions or critical issues without an
> > > acceptable
> > > > workaround to be considered as release blockers.
> > > >
> > > > Exceptions of changes that may be merged to the 3.0 branch without a
> > > > mention on the dev mailing list are fixes for test failures that will
> > > help
> > > > stabilize the build and small documentation changes.
> > > >
> > > > If by the end of this week we are down to zero blockers and have
> green
> > > > builds and passing system tests, I will attempt to generate the first
> > > > Release Candidate (RC) for 3.0.0 on Friday.
> > > >
> > > > Thank you all for the hard work so far.
> > > > Konstantine
> > > >
> > > >
> > > > On Mon, Jul 12, 2021 at 1:59 PM Konstantine Karantasis
> > > >  wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > This is a reminder that Code Freeze for Apache Kafka 3.0 is coming
> up
> > > this
> > > > > week and is set to take place by the end of day Wednesday, July
> 14th.
> > > > >
> > > > > Currently in the project we have 22 blocker issues for 3.0, out of
> 41
> > > total
> > > > > tickets targeting 3.0.
> > > > >
> > > > > You may find the list of open issues in the release plan page:
> > > > >
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> > > > >
> > > > > Thanks for all the hard work so far and for reducing the number of
> open
> > > > > issues in the recent days.
> > > > > Please take another look and help us resolve all the blockers for
> this
> > > > > upcoming major release.
> > > > >
> > > > > Best,
> > > > > Konstantine
> > > > >
> > > > > On Mon, Jul 12, 2021 at 1:57 PM Konstantine Karantasis <
> > > > > konstant...@confluent.io> wrote:
> > > > >
> > > > > >
> > > > > > Thanks for the update Levani,
> > > > > >
> > > > > > KIP-708 is now on the list of postponed KIPs.
> > > > > >
> > > > > > Konstantine
> > > > > >
> > > > > > On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze <
> > > > > levani.co...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[John Roesler]

Hello Konstantine,

Someone just called to my attention that KAFKA-12724 had not
been marked as a 3.0 blocker. We never added 2.8 to the
Streams upgrade system test suite. This isn't a blocker in
that it is a problem, but we should make sure that Streams
is actually upgradable before releasing 3.0.

I'm sorry for the oversight. For what it's worth, I think we
could proceed with a release candidate while we continue to
address the missing system test.

Thanks,
-John

https://issues.apache.org/jira/browse/KAFKA-12724

On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
wrote:
> Thanks for the heads up Colin.
> 
> KAFKA-13112 seems important and of course relevant to what we ship with
> 3.0.
> Same for the test failures captured by KAFKA-13095 and KAFKA-12851. Fixing
> those will increase the stability of our builds.
> 
> Therefore, considering these tickets as blockers currently makes sense to
> me.
> 
> Konstantine
> 
> 
> On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe  wrote:
> 
> > Hi Konstantine,
> > 
> > Thanks for your work on this release! We discovered three blocker bugs
> > which are worth bringing up here:
> > 
> > 1. KAFKA-13112: Controller's committed offset get out of sync with raft
> > client listener context
> > 2. KAFKA-13095: TransactionsTest is failing in kraft mode
> > 3. KAFKA-12851: Flaky Test
> > RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable
> > 
> > There are two subtasks for #1 which we are working on. We suspect that #3
> > has been fixed by a previous fix we made... we're looking into it.
> > 
> > best,
> > Colin
> > 
> > On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> > > Hi all,
> > > 
> > > Since last week, we have reached the stage of Code Freeze for the 3.0.0
> > > Apache Kafka release.
> > > 
> > > From this point forward and until the official release of 3.0.0, only
> > > critical fixes for blocker issues should be merged to the 3.0 release
> > > branch.
> > > 
> > > The release plan currently includes ten (10) such known blockers.
> > > 
> > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> > > 
> > > Besides these issues, any new issue that potentially gets discovered will
> > > need to be reported on dev@kafka.apache.org (under this thread) and be
> > > evaluated as a release blocker. At this point, the bar for such issues is
> > > high; they need to be regressions or critical issues without an
> > acceptable
> > > workaround to be considered as release blockers.
> > > 
> > > Exceptions of changes that may be merged to the 3.0 branch without a
> > > mention on the dev mailing list are fixes for test failures that will
> > help
> > > stabilize the build and small documentation changes.
> > > 
> > > If by the end of this week we are down to zero blockers and have green
> > > builds and passing system tests, I will attempt to generate the first
> > > Release Candidate (RC) for 3.0.0 on Friday.
> > > 
> > > Thank you all for the hard work so far.
> > > Konstantine
> > > 
> > > 
> > > On Mon, Jul 12, 2021 at 1:59 PM Konstantine Karantasis
> > >  wrote:
> > > 
> > > > Hi all,
> > > > 
> > > > This is a reminder that Code Freeze for Apache Kafka 3.0 is coming up
> > this
> > > > week and is set to take place by the end of day Wednesday, July 14th.
> > > > 
> > > > Currently in the project we have 22 blocker issues for 3.0, out of 41
> > total
> > > > tickets targeting 3.0.
> > > > 
> > > > You may find the list of open issues in the release plan page:
> > > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> > > > 
> > > > Thanks for all the hard work so far and for reducing the number of open
> > > > issues in the recent days.
> > > > Please take another look and help us resolve all the blockers for this
> > > > upcoming major release.
> > > > 
> > > > Best,
> > > > Konstantine
> > > > 
> > > > On Mon, Jul 12, 2021 at 1:57 PM Konstantine Karantasis <
> > > > konstant...@confluent.io> wrote:
> > > > 
> > > > > 
> > > > > Thanks for the update Levani,
> > > > > 
> > > > > KIP-708 is now on the list of postponed KIPs.
> > > > > 
> > > > > Konstantine
> > > > > 
> > > > > On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze <
> > > > levani.co...@gmail.com>
> > > > > wrote:
> > > > > 
> > > > > > Hi Konstantine,
> > > > > > 
> > > > > > FYI, I don’t think we will be able to have KIP-708 ready on time.
> > > > > > Feel free to remove it from the release plan.
> > > > > > 
> > > > > > Best,
> > > > > > Levani
> > > > > > 
> > > > > > > On 1. Jul 2021, at 01:27, Konstantine Karantasis <
> > > > > > konstant...@confluent.io.INVALID> wrote:
> > > > > > > 
> > > > > > > Hi all,
> > > > > > > 
> > > > > > > Today we have reached the Feature Freeze milestone for Apache
> > Kafka
> > > > 3.0.
> > > > > > > Exciting!
> > > > > > > 
> > > > > > > I'm going to allow for any pending changes to settle within the
> > next
> > > > > > couple
> > > > > > > of days.
> > > > > > > I trust that we all approve and merge 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for the heads up Colin.

KAFKA-13112 seems important and of course relevant to what we ship with
3.0.
Same for the test failures captured by KAFKA-13095 and KAFKA-12851. Fixing
those will increase the stability of our builds.

Therefore, considering these tickets as blockers currently makes sense to
me.

Konstantine


On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe  wrote:

> Hi Konstantine,
>
> Thanks for your work on this release! We discovered three blocker bugs
> which are worth bringing up here:
>
> 1. KAFKA-13112: Controller's committed offset get out of sync with raft
> client listener context
> 2. KAFKA-13095: TransactionsTest is failing in kraft mode
> 3. KAFKA-12851: Flaky Test
> RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable
>
> There are two subtasks for #1 which we are working on. We suspect that #3
> has been fixed by a previous fix we made... we're looking into it.
>
> best,
> Colin
>
> On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> > Hi all,
> >
> > Since last week, we have reached the stage of Code Freeze for the 3.0.0
> > Apache Kafka release.
> >
> > From this point forward and until the official release of 3.0.0, only
> > critical fixes for blocker issues should be merged to the 3.0 release
> > branch.
> >
> > The release plan currently includes ten (10) such known blockers.
> >
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> >
> > Besides these issues, any new issue that potentially gets discovered will
> > need to be reported on dev@kafka.apache.org (under this thread) and be
> > evaluated as a release blocker. At this point, the bar for such issues is
> > high; they need to be regressions or critical issues without an
> acceptable
> > workaround to be considered as release blockers.
> >
> > Exceptions of changes that may be merged to the 3.0 branch without a
> > mention on the dev mailing list are fixes for test failures that will
> help
> > stabilize the build and small documentation changes.
> >
> > If by the end of this week we are down to zero blockers and have green
> > builds and passing system tests, I will attempt to generate the first
> > Release Candidate (RC) for 3.0.0 on Friday.
> >
> > Thank you all for the hard work so far.
> > Konstantine
> >
> >
> > On Mon, Jul 12, 2021 at 1:59 PM Konstantine Karantasis
> >  wrote:
> >
> > > Hi all,
> > >
> > > This is a reminder that Code Freeze for Apache Kafka 3.0 is coming up
> this
> > > week and is set to take place by the end of day Wednesday, July 14th.
> > >
> > > Currently in the project we have 22 blocker issues for 3.0, out of 41
> total
> > > tickets targeting 3.0.
> > >
> > > You may find the list of open issues in the release plan page:
> > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> > >
> > > Thanks for all the hard work so far and for reducing the number of open
> > > issues in the recent days.
> > > Please take another look and help us resolve all the blockers for this
> > > upcoming major release.
> > >
> > > Best,
> > > Konstantine
> > >
> > > On Mon, Jul 12, 2021 at 1:57 PM Konstantine Karantasis <
> > > konstant...@confluent.io> wrote:
> > >
> > > >
> > > > Thanks for the update Levani,
> > > >
> > > > KIP-708 is now on the list of postponed KIPs.
> > > >
> > > > Konstantine
> > > >
> > > > On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze <
> > > levani.co...@gmail.com>
> > > > wrote:
> > > >
> > > >> Hi Konstantine,
> > > >>
> > > >> FYI, I don’t think we will be able to have KIP-708 ready on time.
> > > >> Feel free to remove it from the release plan.
> > > >>
> > > >> Best,
> > > >> Levani
> > > >>
> > > >> > On 1. Jul 2021, at 01:27, Konstantine Karantasis <
> > > >> konstant...@confluent.io.INVALID> wrote:
> > > >> >
> > > >> > Hi all,
> > > >> >
> > > >> > Today we have reached the Feature Freeze milestone for Apache
> Kafka
> > > 3.0.
> > > >> > Exciting!
> > > >> >
> > > >> > I'm going to allow for any pending changes to settle within the
> next
> > > >> couple
> > > >> > of days.
> > > >> > I trust that we all approve and merge adopted features and changes
> > > >> which we
> > > >> > consider to be in good shape for 3.0.
> > > >> >
> > > >> > Given the 4th of July holiday in the US, the 3.0 release branch
> will
> > > >> appear
> > > >> > sometime on Tuesday, July 6th.
> > > >> > Until then, please keep merging to trunk only the changes you
> intend
> > > to
> > > >> > include in Apache Kafka 3.0.
> > > >> >
> > > >> > Regards,
> > > >> > Konstantine
> > > >> >
> > > >> >
> > > >> > On Wed, Jun 30, 2021 at 3:25 PM Konstantine Karantasis <
> > > >> > konstant...@confluent.io> wrote:
> > > >> >
> > > >> >>
> > > >> >> Done. Thanks Luke!
> > > >> >>
> > > >> >> On Tue, Jun 29, 2021 at 6:39 PM Luke Chen 
> wrote:
> > > >> >>
> > > >> >>> Hi Konstantine,
> > > >> >>> We've decided that the KIP-726 will be released in V3.1, not
> V3.0.
> > > >> >>> KIP-726: Make the "cooperative-sticky, range" as the default
> > > 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Colin McCabe]

Hi Konstantine,

Thanks for your work on this release! We discovered three blocker bugs which 
are worth bringing up here:

1. KAFKA-13112: Controller's committed offset get out of sync with raft client 
listener context
2. KAFKA-13095: TransactionsTest is failing in kraft mode
3. KAFKA-12851: Flaky Test 
RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable

There are two subtasks for #1 which we are working on. We suspect that #3 has 
been fixed by a previous fix we made... we're looking into it.

best,
Colin

On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> Hi all,
> 
> Since last week, we have reached the stage of Code Freeze for the 3.0.0
> Apache Kafka release.
> 
> From this point forward and until the official release of 3.0.0, only
> critical fixes for blocker issues should be merged to the 3.0 release
> branch.
> 
> The release plan currently includes ten (10) such known blockers.
> 
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> 
> Besides these issues, any new issue that potentially gets discovered will
> need to be reported on dev@kafka.apache.org (under this thread) and be
> evaluated as a release blocker. At this point, the bar for such issues is
> high; they need to be regressions or critical issues without an acceptable
> workaround to be considered as release blockers.
> 
> Exceptions of changes that may be merged to the 3.0 branch without a
> mention on the dev mailing list are fixes for test failures that will help
> stabilize the build and small documentation changes.
> 
> If by the end of this week we are down to zero blockers and have green
> builds and passing system tests, I will attempt to generate the first
> Release Candidate (RC) for 3.0.0 on Friday.
> 
> Thank you all for the hard work so far.
> Konstantine
> 
> 
> On Mon, Jul 12, 2021 at 1:59 PM Konstantine Karantasis
>  wrote:
> 
> > Hi all,
> >
> > This is a reminder that Code Freeze for Apache Kafka 3.0 is coming up this
> > week and is set to take place by the end of day Wednesday, July 14th.
> >
> > Currently in the project we have 22 blocker issues for 3.0, out of 41 total
> > tickets targeting 3.0.
> >
> > You may find the list of open issues in the release plan page:
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> >
> > Thanks for all the hard work so far and for reducing the number of open
> > issues in the recent days.
> > Please take another look and help us resolve all the blockers for this
> > upcoming major release.
> >
> > Best,
> > Konstantine
> >
> > On Mon, Jul 12, 2021 at 1:57 PM Konstantine Karantasis <
> > konstant...@confluent.io> wrote:
> >
> > >
> > > Thanks for the update Levani,
> > >
> > > KIP-708 is now on the list of postponed KIPs.
> > >
> > > Konstantine
> > >
> > > On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze <
> > levani.co...@gmail.com>
> > > wrote:
> > >
> > >> Hi Konstantine,
> > >>
> > >> FYI, I don’t think we will be able to have KIP-708 ready on time.
> > >> Feel free to remove it from the release plan.
> > >>
> > >> Best,
> > >> Levani
> > >>
> > >> > On 1. Jul 2021, at 01:27, Konstantine Karantasis <
> > >> konstant...@confluent.io.INVALID> wrote:
> > >> >
> > >> > Hi all,
> > >> >
> > >> > Today we have reached the Feature Freeze milestone for Apache Kafka
> > 3.0.
> > >> > Exciting!
> > >> >
> > >> > I'm going to allow for any pending changes to settle within the next
> > >> couple
> > >> > of days.
> > >> > I trust that we all approve and merge adopted features and changes
> > >> which we
> > >> > consider to be in good shape for 3.0.
> > >> >
> > >> > Given the 4th of July holiday in the US, the 3.0 release branch will
> > >> appear
> > >> > sometime on Tuesday, July 6th.
> > >> > Until then, please keep merging to trunk only the changes you intend
> > to
> > >> > include in Apache Kafka 3.0.
> > >> >
> > >> > Regards,
> > >> > Konstantine
> > >> >
> > >> >
> > >> > On Wed, Jun 30, 2021 at 3:25 PM Konstantine Karantasis <
> > >> > konstant...@confluent.io> wrote:
> > >> >
> > >> >>
> > >> >> Done. Thanks Luke!
> > >> >>
> > >> >> On Tue, Jun 29, 2021 at 6:39 PM Luke Chen  wrote:
> > >> >>
> > >> >>> Hi Konstantine,
> > >> >>> We've decided that the KIP-726 will be released in V3.1, not V3.0.
> > >> >>> KIP-726: Make the "cooperative-sticky, range" as the default
> > assignor
> > >> >>>
> > >> >>> Could you please remove this KIP from the 3.0 release plan wiki
> > page?
> > >> >>>
> > >> >>> Thank you.
> > >> >>> Luke
> > >> >>>
> > >> >>> On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
> > >> >>>  wrote:
> > >> >>>
> > >>  Thanks for the update Colin.
> > >>  They are now both in the release plan.
> > >> 
> > >>  Best,
> > >>  Konstantine
> > >> 
> > >>  On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe 
> > >> >>> wrote:
> > >> 
> > >> > Hi Konstantine,
> > >> >
> > >> > Can you please add two KIPs to the 3.0 release plan wiki page?
> > >> >
> > >> 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi all,

Since last week, we have reached the stage of Code Freeze for the 3.0.0
Apache Kafka release.

>From this point forward and until the official release of 3.0.0, only
critical fixes for blocker issues should be merged to the 3.0 release
branch.

The release plan currently includes ten (10) such known blockers.

https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0

Besides these issues, any new issue that potentially gets discovered will
need to be reported on dev@kafka.apache.org (under this thread) and be
evaluated as a release blocker. At this point, the bar for such issues is
high; they need to be regressions or critical issues without an acceptable
workaround to be considered as release blockers.

Exceptions of changes that may be merged to the 3.0 branch without a
mention on the dev mailing list are fixes for test failures that will help
stabilize the build and small documentation changes.

If by the end of this week we are down to zero blockers and have green
builds and passing system tests, I will attempt to generate the first
Release Candidate (RC) for 3.0.0 on Friday.

Thank you all for the hard work so far.
Konstantine


On Mon, Jul 12, 2021 at 1:59 PM Konstantine Karantasis
 wrote:

> Hi all,
>
> This is a reminder that Code Freeze for Apache Kafka 3.0 is coming up this
> week and is set to take place by the end of day Wednesday, July 14th.
>
> Currently in the project we have 22 blocker issues for 3.0, out of 41 total
> tickets targeting 3.0.
>
> You may find the list of open issues in the release plan page:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
>
> Thanks for all the hard work so far and for reducing the number of open
> issues in the recent days.
> Please take another look and help us resolve all the blockers for this
> upcoming major release.
>
> Best,
> Konstantine
>
> On Mon, Jul 12, 2021 at 1:57 PM Konstantine Karantasis <
> konstant...@confluent.io> wrote:
>
> >
> > Thanks for the update Levani,
> >
> > KIP-708 is now on the list of postponed KIPs.
> >
> > Konstantine
> >
> > On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze <
> levani.co...@gmail.com>
> > wrote:
> >
> >> Hi Konstantine,
> >>
> >> FYI, I don’t think we will be able to have KIP-708 ready on time.
> >> Feel free to remove it from the release plan.
> >>
> >> Best,
> >> Levani
> >>
> >> > On 1. Jul 2021, at 01:27, Konstantine Karantasis <
> >> konstant...@confluent.io.INVALID> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > Today we have reached the Feature Freeze milestone for Apache Kafka
> 3.0.
> >> > Exciting!
> >> >
> >> > I'm going to allow for any pending changes to settle within the next
> >> couple
> >> > of days.
> >> > I trust that we all approve and merge adopted features and changes
> >> which we
> >> > consider to be in good shape for 3.0.
> >> >
> >> > Given the 4th of July holiday in the US, the 3.0 release branch will
> >> appear
> >> > sometime on Tuesday, July 6th.
> >> > Until then, please keep merging to trunk only the changes you intend
> to
> >> > include in Apache Kafka 3.0.
> >> >
> >> > Regards,
> >> > Konstantine
> >> >
> >> >
> >> > On Wed, Jun 30, 2021 at 3:25 PM Konstantine Karantasis <
> >> > konstant...@confluent.io> wrote:
> >> >
> >> >>
> >> >> Done. Thanks Luke!
> >> >>
> >> >> On Tue, Jun 29, 2021 at 6:39 PM Luke Chen  wrote:
> >> >>
> >> >>> Hi Konstantine,
> >> >>> We've decided that the KIP-726 will be released in V3.1, not V3.0.
> >> >>> KIP-726: Make the "cooperative-sticky, range" as the default
> assignor
> >> >>>
> >> >>> Could you please remove this KIP from the 3.0 release plan wiki
> page?
> >> >>>
> >> >>> Thank you.
> >> >>> Luke
> >> >>>
> >> >>> On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
> >> >>>  wrote:
> >> >>>
> >>  Thanks for the update Colin.
> >>  They are now both in the release plan.
> >> 
> >>  Best,
> >>  Konstantine
> >> 
> >>  On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe 
> >> >>> wrote:
> >> 
> >> > Hi Konstantine,
> >> >
> >> > Can you please add two KIPs to the 3.0 release plan wiki page?
> >> >
> >> > I'm thinking of:
> >> >KIP-630: Kafka Raft Snapshots
> >> >KIP-746: Revise KRaft Metadata Records
> >> >
> >> > These are marked as 3.0 on the KIP page but I guess we don't have
> >> >>> them on
> >> > the page yet.
> >> >
> >> > Many thanks.
> >> > Colin
> >> >
> >> >
> >> > On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
> >> >> Hi there,
> >> >>
> >> >> As the feature freeze date is approaching, I just wanted to
> kindly
> >> >>> ask
> >> > for
> >> >> some reviews on the already submitted PR (
> >> >> https://github.com/apache/kafka/pull/10840) that implements the
> >>  approved
> >> >> KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR
> has
> >>  been
> >> >> ready for review for 2 weeks, and I simply want to make sure
> there
> >> >>> 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi all,

This is a reminder that Code Freeze for Apache Kafka 3.0 is coming up this
week and is set to take place by the end of day Wednesday, July 14th.

Currently in the project we have 22 blocker issues for 3.0, out of 41 total
tickets targeting 3.0.

You may find the list of open issues in the release plan page:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0

Thanks for all the hard work so far and for reducing the number of open
issues in the recent days.
Please take another look and help us resolve all the blockers for this
upcoming major release.

Best,
Konstantine

On Mon, Jul 12, 2021 at 1:57 PM Konstantine Karantasis <
konstant...@confluent.io> wrote:

>
> Thanks for the update Levani,
>
> KIP-708 is now on the list of postponed KIPs.
>
> Konstantine
>
> On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze 
> wrote:
>
>> Hi Konstantine,
>>
>> FYI, I don’t think we will be able to have KIP-708 ready on time.
>> Feel free to remove it from the release plan.
>>
>> Best,
>> Levani
>>
>> > On 1. Jul 2021, at 01:27, Konstantine Karantasis <
>> konstant...@confluent.io.INVALID> wrote:
>> >
>> > Hi all,
>> >
>> > Today we have reached the Feature Freeze milestone for Apache Kafka 3.0.
>> > Exciting!
>> >
>> > I'm going to allow for any pending changes to settle within the next
>> couple
>> > of days.
>> > I trust that we all approve and merge adopted features and changes
>> which we
>> > consider to be in good shape for 3.0.
>> >
>> > Given the 4th of July holiday in the US, the 3.0 release branch will
>> appear
>> > sometime on Tuesday, July 6th.
>> > Until then, please keep merging to trunk only the changes you intend to
>> > include in Apache Kafka 3.0.
>> >
>> > Regards,
>> > Konstantine
>> >
>> >
>> > On Wed, Jun 30, 2021 at 3:25 PM Konstantine Karantasis <
>> > konstant...@confluent.io> wrote:
>> >
>> >>
>> >> Done. Thanks Luke!
>> >>
>> >> On Tue, Jun 29, 2021 at 6:39 PM Luke Chen  wrote:
>> >>
>> >>> Hi Konstantine,
>> >>> We've decided that the KIP-726 will be released in V3.1, not V3.0.
>> >>> KIP-726: Make the "cooperative-sticky, range" as the default assignor
>> >>>
>> >>> Could you please remove this KIP from the 3.0 release plan wiki page?
>> >>>
>> >>> Thank you.
>> >>> Luke
>> >>>
>> >>> On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
>> >>>  wrote:
>> >>>
>>  Thanks for the update Colin.
>>  They are now both in the release plan.
>> 
>>  Best,
>>  Konstantine
>> 
>>  On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe 
>> >>> wrote:
>> 
>> > Hi Konstantine,
>> >
>> > Can you please add two KIPs to the 3.0 release plan wiki page?
>> >
>> > I'm thinking of:
>> >KIP-630: Kafka Raft Snapshots
>> >KIP-746: Revise KRaft Metadata Records
>> >
>> > These are marked as 3.0 on the KIP page but I guess we don't have
>> >>> them on
>> > the page yet.
>> >
>> > Many thanks.
>> > Colin
>> >
>> >
>> > On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
>> >> Hi there,
>> >>
>> >> As the feature freeze date is approaching, I just wanted to kindly
>> >>> ask
>> > for
>> >> some reviews on the already submitted PR (
>> >> https://github.com/apache/kafka/pull/10840) that implements the
>>  approved
>> >> KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has
>>  been
>> >> ready for review for 2 weeks, and I simply want to make sure there
>> >>> is
>> >> enough time to address any possible changes that might be
>> requested.
>> >>
>> >> Thanks in advance and sorry for any inconvenience caused,
>> >> --
>> >> Josep
>> >> On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
>> >>  wrote:
>> >>
>> >>> Thanks for the update Bruno.
>> >>> I've moved KIP-698 to the list of postponed KIPs in the plan.
>> >>>
>> >>> Konstantine
>> >>>
>> >>> On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna > 
>> > wrote:
>> >>>
>>  Hi Konstantine,
>> 
>>  The implementation of
>> 
>>  KIP-698: Add Explicit User Initialization of Broker-side State
>> >>> to
>> > Kafka
>>  Streams
>> 
>>  will not be ready for 3.0, so you can remove it from the list.
>> 
>>  Best,
>>  Bruno
>> 
>>  On 15.06.21 07:33, Konstantine Karantasis wrote:
>> > Done. Moved it into the table of Adopted KIPs targeting 3.0.0
>> >>> and
>> > to
>> >>> the
>> > release plan of course.
>> > Thanks for catching this Israel.
>> >
>> > Best,
>> > Konstantine
>> >
>> > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo <
>>  israele...@gmail.com>
>>  wrote:
>> >
>> >> Konstantine,
>> >>
>> >> One of mine is missing from this list
>> >>
>> >> KIP-633: Drop 24 hour default of grace period in Streams
>> 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for the update Levani,

KIP-708 is now on the list of postponed KIPs.

Konstantine

On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze 
wrote:

> Hi Konstantine,
>
> FYI, I don’t think we will be able to have KIP-708 ready on time.
> Feel free to remove it from the release plan.
>
> Best,
> Levani
>
> > On 1. Jul 2021, at 01:27, Konstantine Karantasis <
> konstant...@confluent.io.INVALID> wrote:
> >
> > Hi all,
> >
> > Today we have reached the Feature Freeze milestone for Apache Kafka 3.0.
> > Exciting!
> >
> > I'm going to allow for any pending changes to settle within the next
> couple
> > of days.
> > I trust that we all approve and merge adopted features and changes which
> we
> > consider to be in good shape for 3.0.
> >
> > Given the 4th of July holiday in the US, the 3.0 release branch will
> appear
> > sometime on Tuesday, July 6th.
> > Until then, please keep merging to trunk only the changes you intend to
> > include in Apache Kafka 3.0.
> >
> > Regards,
> > Konstantine
> >
> >
> > On Wed, Jun 30, 2021 at 3:25 PM Konstantine Karantasis <
> > konstant...@confluent.io> wrote:
> >
> >>
> >> Done. Thanks Luke!
> >>
> >> On Tue, Jun 29, 2021 at 6:39 PM Luke Chen  wrote:
> >>
> >>> Hi Konstantine,
> >>> We've decided that the KIP-726 will be released in V3.1, not V3.0.
> >>> KIP-726: Make the "cooperative-sticky, range" as the default assignor
> >>>
> >>> Could you please remove this KIP from the 3.0 release plan wiki page?
> >>>
> >>> Thank you.
> >>> Luke
> >>>
> >>> On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
> >>>  wrote:
> >>>
>  Thanks for the update Colin.
>  They are now both in the release plan.
> 
>  Best,
>  Konstantine
> 
>  On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe 
> >>> wrote:
> 
> > Hi Konstantine,
> >
> > Can you please add two KIPs to the 3.0 release plan wiki page?
> >
> > I'm thinking of:
> >KIP-630: Kafka Raft Snapshots
> >KIP-746: Revise KRaft Metadata Records
> >
> > These are marked as 3.0 on the KIP page but I guess we don't have
> >>> them on
> > the page yet.
> >
> > Many thanks.
> > Colin
> >
> >
> > On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
> >> Hi there,
> >>
> >> As the feature freeze date is approaching, I just wanted to kindly
> >>> ask
> > for
> >> some reviews on the already submitted PR (
> >> https://github.com/apache/kafka/pull/10840) that implements the
>  approved
> >> KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has
>  been
> >> ready for review for 2 weeks, and I simply want to make sure there
> >>> is
> >> enough time to address any possible changes that might be requested.
> >>
> >> Thanks in advance and sorry for any inconvenience caused,
> >> --
> >> Josep
> >> On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
> >>  wrote:
> >>
> >>> Thanks for the update Bruno.
> >>> I've moved KIP-698 to the list of postponed KIPs in the plan.
> >>>
> >>> Konstantine
> >>>
> >>> On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna  
> > wrote:
> >>>
>  Hi Konstantine,
> 
>  The implementation of
> 
>  KIP-698: Add Explicit User Initialization of Broker-side State
> >>> to
> > Kafka
>  Streams
> 
>  will not be ready for 3.0, so you can remove it from the list.
> 
>  Best,
>  Bruno
> 
>  On 15.06.21 07:33, Konstantine Karantasis wrote:
> > Done. Moved it into the table of Adopted KIPs targeting 3.0.0
> >>> and
> > to
> >>> the
> > release plan of course.
> > Thanks for catching this Israel.
> >
> > Best,
> > Konstantine
> >
> > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo <
>  israele...@gmail.com>
>  wrote:
> >
> >> Konstantine,
> >>
> >> One of mine is missing from this list
> >>
> >> KIP-633: Drop 24 hour default of grace period in Streams
> >> Please could you include it?
> >>
> >> Voting has already concluded a long time ago
> >>
> >>
> >>
> >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
> >>  wrote:
> >>
> >>> Hi all.
> >>>
> >>> KIP Freeze for the next major release of Apache Kafka was
>  reached
> >>> last
> >>> week.
> >>>
> >>> As of now, 36 KIPs have concluded their voting process and
> >>> have
> > been
> >>> adopted.
> >>> These KIPs are targeting 3.0 (unless it's noted otherwise in
>  the
>  release
> >>> plan) and their inclusion as new features will be finalized
>  right
> >>> after
> >>> Feature Freeze.
> >>>
> >>> At the high level, out of these 36 KIPs, 11 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Levani Kokhreidze]

Hi Konstantine,

FYI, I don’t think we will be able to have KIP-708 ready on time.
Feel free to remove it from the release plan.

Best,
Levani

> On 1. Jul 2021, at 01:27, Konstantine Karantasis 
>  wrote:
> 
> Hi all,
> 
> Today we have reached the Feature Freeze milestone for Apache Kafka 3.0.
> Exciting!
> 
> I'm going to allow for any pending changes to settle within the next couple
> of days.
> I trust that we all approve and merge adopted features and changes which we
> consider to be in good shape for 3.0.
> 
> Given the 4th of July holiday in the US, the 3.0 release branch will appear
> sometime on Tuesday, July 6th.
> Until then, please keep merging to trunk only the changes you intend to
> include in Apache Kafka 3.0.
> 
> Regards,
> Konstantine
> 
> 
> On Wed, Jun 30, 2021 at 3:25 PM Konstantine Karantasis <
> konstant...@confluent.io> wrote:
> 
>> 
>> Done. Thanks Luke!
>> 
>> On Tue, Jun 29, 2021 at 6:39 PM Luke Chen  wrote:
>> 
>>> Hi Konstantine,
>>> We've decided that the KIP-726 will be released in V3.1, not V3.0.
>>> KIP-726: Make the "cooperative-sticky, range" as the default assignor
>>> 
>>> Could you please remove this KIP from the 3.0 release plan wiki page?
>>> 
>>> Thank you.
>>> Luke
>>> 
>>> On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
>>>  wrote:
>>> 
 Thanks for the update Colin.
 They are now both in the release plan.
 
 Best,
 Konstantine
 
 On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe 
>>> wrote:
 
> Hi Konstantine,
> 
> Can you please add two KIPs to the 3.0 release plan wiki page?
> 
> I'm thinking of:
>KIP-630: Kafka Raft Snapshots
>KIP-746: Revise KRaft Metadata Records
> 
> These are marked as 3.0 on the KIP page but I guess we don't have
>>> them on
> the page yet.
> 
> Many thanks.
> Colin
> 
> 
> On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
>> Hi there,
>> 
>> As the feature freeze date is approaching, I just wanted to kindly
>>> ask
> for
>> some reviews on the already submitted PR (
>> https://github.com/apache/kafka/pull/10840) that implements the
 approved
>> KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has
 been
>> ready for review for 2 weeks, and I simply want to make sure there
>>> is
>> enough time to address any possible changes that might be requested.
>> 
>> Thanks in advance and sorry for any inconvenience caused,
>> --
>> Josep
>> On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
>>  wrote:
>> 
>>> Thanks for the update Bruno.
>>> I've moved KIP-698 to the list of postponed KIPs in the plan.
>>> 
>>> Konstantine
>>> 
>>> On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna >>> 
> wrote:
>>> 
 Hi Konstantine,
 
 The implementation of
 
 KIP-698: Add Explicit User Initialization of Broker-side State
>>> to
> Kafka
 Streams
 
 will not be ready for 3.0, so you can remove it from the list.
 
 Best,
 Bruno
 
 On 15.06.21 07:33, Konstantine Karantasis wrote:
> Done. Moved it into the table of Adopted KIPs targeting 3.0.0
>>> and
> to
>>> the
> release plan of course.
> Thanks for catching this Israel.
> 
> Best,
> Konstantine
> 
> On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo <
 israele...@gmail.com>
 wrote:
> 
>> Konstantine,
>> 
>> One of mine is missing from this list
>> 
>> KIP-633: Drop 24 hour default of grace period in Streams
>> Please could you include it?
>> 
>> Voting has already concluded a long time ago
>> 
>> 
>> 
>> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
>>  wrote:
>> 
>>> Hi all.
>>> 
>>> KIP Freeze for the next major release of Apache Kafka was
 reached
>>> last
>>> week.
>>> 
>>> As of now, 36 KIPs have concluded their voting process and
>>> have
> been
>>> adopted.
>>> These KIPs are targeting 3.0 (unless it's noted otherwise in
 the
 release
>>> plan) and their inclusion as new features will be finalized
 right
>>> after
>>> Feature Freeze.
>>> 
>>> At the high level, out of these 36 KIPs, 11 have been
 implemented
 already
>>> and 25 are open or in progress.
>>> Here is the full list of adopted KIPs:
>>> 
>>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0
>>> (deprecate in
> 3.0)
>>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in
 3.0)
>>> KIP-746: Revise KRaft Metadata Records
>>> KIP-745: Connect API to restart connector and tasks
>>> KIP-744: Migrate 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi all,

Today we have reached the Feature Freeze milestone for Apache Kafka 3.0.
Exciting!

I'm going to allow for any pending changes to settle within the next couple
of days.
I trust that we all approve and merge adopted features and changes which we
consider to be in good shape for 3.0.

Given the 4th of July holiday in the US, the 3.0 release branch will appear
sometime on Tuesday, July 6th.
Until then, please keep merging to trunk only the changes you intend to
include in Apache Kafka 3.0.

Regards,
Konstantine


On Wed, Jun 30, 2021 at 3:25 PM Konstantine Karantasis <
konstant...@confluent.io> wrote:

>
> Done. Thanks Luke!
>
> On Tue, Jun 29, 2021 at 6:39 PM Luke Chen  wrote:
>
>> Hi Konstantine,
>> We've decided that the KIP-726 will be released in V3.1, not V3.0.
>> KIP-726: Make the "cooperative-sticky, range" as the default assignor
>>
>> Could you please remove this KIP from the 3.0 release plan wiki page?
>>
>> Thank you.
>> Luke
>>
>> On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
>>  wrote:
>>
>> > Thanks for the update Colin.
>> > They are now both in the release plan.
>> >
>> > Best,
>> > Konstantine
>> >
>> > On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe 
>> wrote:
>> >
>> > > Hi Konstantine,
>> > >
>> > > Can you please add two KIPs to the 3.0 release plan wiki page?
>> > >
>> > > I'm thinking of:
>> > > KIP-630: Kafka Raft Snapshots
>> > > KIP-746: Revise KRaft Metadata Records
>> > >
>> > > These are marked as 3.0 on the KIP page but I guess we don't have
>> them on
>> > > the page yet.
>> > >
>> > > Many thanks.
>> > > Colin
>> > >
>> > >
>> > > On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
>> > > > Hi there,
>> > > >
>> > > > As the feature freeze date is approaching, I just wanted to kindly
>> ask
>> > > for
>> > > > some reviews on the already submitted PR (
>> > > > https://github.com/apache/kafka/pull/10840) that implements the
>> > approved
>> > > > KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has
>> > been
>> > > > ready for review for 2 weeks, and I simply want to make sure there
>> is
>> > > > enough time to address any possible changes that might be requested.
>> > > >
>> > > > Thanks in advance and sorry for any inconvenience caused,
>> > > > --
>> > > > Josep
>> > > > On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
>> > > >  wrote:
>> > > >
>> > > > > Thanks for the update Bruno.
>> > > > > I've moved KIP-698 to the list of postponed KIPs in the plan.
>> > > > >
>> > > > > Konstantine
>> > > > >
>> > > > > On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna > >
>> > > wrote:
>> > > > >
>> > > > > > Hi Konstantine,
>> > > > > >
>> > > > > > The implementation of
>> > > > > >
>> > > > > > KIP-698: Add Explicit User Initialization of Broker-side State
>> to
>> > > Kafka
>> > > > > > Streams
>> > > > > >
>> > > > > > will not be ready for 3.0, so you can remove it from the list.
>> > > > > >
>> > > > > > Best,
>> > > > > > Bruno
>> > > > > >
>> > > > > > On 15.06.21 07:33, Konstantine Karantasis wrote:
>> > > > > > > Done. Moved it into the table of Adopted KIPs targeting 3.0.0
>> and
>> > > to
>> > > > > the
>> > > > > > > release plan of course.
>> > > > > > > Thanks for catching this Israel.
>> > > > > > >
>> > > > > > > Best,
>> > > > > > > Konstantine
>> > > > > > >
>> > > > > > > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo <
>> > israele...@gmail.com>
>> > > > > > wrote:
>> > > > > > >
>> > > > > > >> Konstantine,
>> > > > > > >>
>> > > > > > >> One of mine is missing from this list
>> > > > > > >>
>> > > > > > >> KIP-633: Drop 24 hour default of grace period in Streams
>> > > > > > >> Please could you include it?
>> > > > > > >>
>> > > > > > >> Voting has already concluded a long time ago
>> > > > > > >>
>> > > > > > >>
>> > > > > > >>
>> > > > > > >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
>> > > > > > >>  wrote:
>> > > > > > >>
>> > > > > > >>> Hi all.
>> > > > > > >>>
>> > > > > > >>> KIP Freeze for the next major release of Apache Kafka was
>> > reached
>> > > > > last
>> > > > > > >>> week.
>> > > > > > >>>
>> > > > > > >>> As of now, 36 KIPs have concluded their voting process and
>> have
>> > > been
>> > > > > > >>> adopted.
>> > > > > > >>> These KIPs are targeting 3.0 (unless it's noted otherwise in
>> > the
>> > > > > > release
>> > > > > > >>> plan) and their inclusion as new features will be finalized
>> > right
>> > > > > after
>> > > > > > >>> Feature Freeze.
>> > > > > > >>>
>> > > > > > >>> At the high level, out of these 36 KIPs, 11 have been
>> > implemented
>> > > > > > already
>> > > > > > >>> and 25 are open or in progress.
>> > > > > > >>> Here is the full list of adopted KIPs:
>> > > > > > >>>
>> > > > > > >>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0
>> (deprecate in
>> > > 3.0)
>> > > > > > >>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in
>> > 3.0)
>> > > > > > >>> KIP-746: Revise KRaft Metadata Records
>> > > > > > >>> KIP-745: Connect API to restart connector and 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Done. Thanks Luke!

On Tue, Jun 29, 2021 at 6:39 PM Luke Chen  wrote:

> Hi Konstantine,
> We've decided that the KIP-726 will be released in V3.1, not V3.0.
> KIP-726: Make the "cooperative-sticky, range" as the default assignor
>
> Could you please remove this KIP from the 3.0 release plan wiki page?
>
> Thank you.
> Luke
>
> On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
>  wrote:
>
> > Thanks for the update Colin.
> > They are now both in the release plan.
> >
> > Best,
> > Konstantine
> >
> > On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe  wrote:
> >
> > > Hi Konstantine,
> > >
> > > Can you please add two KIPs to the 3.0 release plan wiki page?
> > >
> > > I'm thinking of:
> > > KIP-630: Kafka Raft Snapshots
> > > KIP-746: Revise KRaft Metadata Records
> > >
> > > These are marked as 3.0 on the KIP page but I guess we don't have them
> on
> > > the page yet.
> > >
> > > Many thanks.
> > > Colin
> > >
> > >
> > > On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
> > > > Hi there,
> > > >
> > > > As the feature freeze date is approaching, I just wanted to kindly
> ask
> > > for
> > > > some reviews on the already submitted PR (
> > > > https://github.com/apache/kafka/pull/10840) that implements the
> > approved
> > > > KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has
> > been
> > > > ready for review for 2 weeks, and I simply want to make sure there is
> > > > enough time to address any possible changes that might be requested.
> > > >
> > > > Thanks in advance and sorry for any inconvenience caused,
> > > > --
> > > > Josep
> > > > On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
> > > >  wrote:
> > > >
> > > > > Thanks for the update Bruno.
> > > > > I've moved KIP-698 to the list of postponed KIPs in the plan.
> > > > >
> > > > > Konstantine
> > > > >
> > > > > On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna 
> > > wrote:
> > > > >
> > > > > > Hi Konstantine,
> > > > > >
> > > > > > The implementation of
> > > > > >
> > > > > > KIP-698: Add Explicit User Initialization of Broker-side State to
> > > Kafka
> > > > > > Streams
> > > > > >
> > > > > > will not be ready for 3.0, so you can remove it from the list.
> > > > > >
> > > > > > Best,
> > > > > > Bruno
> > > > > >
> > > > > > On 15.06.21 07:33, Konstantine Karantasis wrote:
> > > > > > > Done. Moved it into the table of Adopted KIPs targeting 3.0.0
> and
> > > to
> > > > > the
> > > > > > > release plan of course.
> > > > > > > Thanks for catching this Israel.
> > > > > > >
> > > > > > > Best,
> > > > > > > Konstantine
> > > > > > >
> > > > > > > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo <
> > israele...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > >> Konstantine,
> > > > > > >>
> > > > > > >> One of mine is missing from this list
> > > > > > >>
> > > > > > >> KIP-633: Drop 24 hour default of grace period in Streams
> > > > > > >> Please could you include it?
> > > > > > >>
> > > > > > >> Voting has already concluded a long time ago
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
> > > > > > >>  wrote:
> > > > > > >>
> > > > > > >>> Hi all.
> > > > > > >>>
> > > > > > >>> KIP Freeze for the next major release of Apache Kafka was
> > reached
> > > > > last
> > > > > > >>> week.
> > > > > > >>>
> > > > > > >>> As of now, 36 KIPs have concluded their voting process and
> have
> > > been
> > > > > > >>> adopted.
> > > > > > >>> These KIPs are targeting 3.0 (unless it's noted otherwise in
> > the
> > > > > > release
> > > > > > >>> plan) and their inclusion as new features will be finalized
> > right
> > > > > after
> > > > > > >>> Feature Freeze.
> > > > > > >>>
> > > > > > >>> At the high level, out of these 36 KIPs, 11 have been
> > implemented
> > > > > > already
> > > > > > >>> and 25 are open or in progress.
> > > > > > >>> Here is the full list of adopted KIPs:
> > > > > > >>>
> > > > > > >>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate
> in
> > > 3.0)
> > > > > > >>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in
> > 3.0)
> > > > > > >>> KIP-746: Revise KRaft Metadata Records
> > > > > > >>> KIP-745: Connect API to restart connector and tasks
> > > > > > >>> KIP-744: Migrate TaskMetadata and ThreadMetadata to an
> > interface
> > > with
> > > > > > >>> internal implementation
> > > > > > >>> KIP-743: Remove config value 0.10.0-2.4 of Streams built-in
> > > metrics
> > > > > > >> version
> > > > > > >>> config
> > > > > > >>> KIP-741: Change default serde to be null
> > > > > > >>> KIP-740: Clean up public API in TaskId and fix
> > > TaskMetadata#taskId()
> > > > > > >>> KIP-738: Removal of Connect's internal converter properties
> > > > > > >>> KIP-734: Improve AdminClient.listOffsets to return timestamp
> > and
> > > > > offset
> > > > > > >> for
> > > > > > >>> the record with the largest timestamp
> > > > > > >>> KIP-733: Change Kafka Streams default replication factor
> config
> > > > > > >>> 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Luke Chen]

Hi Konstantine,
We've decided that the KIP-726 will be released in V3.1, not V3.0.
KIP-726: Make the "cooperative-sticky, range" as the default assignor

Could you please remove this KIP from the 3.0 release plan wiki page?

Thank you.
Luke

On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
 wrote:

> Thanks for the update Colin.
> They are now both in the release plan.
>
> Best,
> Konstantine
>
> On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe  wrote:
>
> > Hi Konstantine,
> >
> > Can you please add two KIPs to the 3.0 release plan wiki page?
> >
> > I'm thinking of:
> > KIP-630: Kafka Raft Snapshots
> > KIP-746: Revise KRaft Metadata Records
> >
> > These are marked as 3.0 on the KIP page but I guess we don't have them on
> > the page yet.
> >
> > Many thanks.
> > Colin
> >
> >
> > On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
> > > Hi there,
> > >
> > > As the feature freeze date is approaching, I just wanted to kindly ask
> > for
> > > some reviews on the already submitted PR (
> > > https://github.com/apache/kafka/pull/10840) that implements the
> approved
> > > KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has
> been
> > > ready for review for 2 weeks, and I simply want to make sure there is
> > > enough time to address any possible changes that might be requested.
> > >
> > > Thanks in advance and sorry for any inconvenience caused,
> > > --
> > > Josep
> > > On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
> > >  wrote:
> > >
> > > > Thanks for the update Bruno.
> > > > I've moved KIP-698 to the list of postponed KIPs in the plan.
> > > >
> > > > Konstantine
> > > >
> > > > On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna 
> > wrote:
> > > >
> > > > > Hi Konstantine,
> > > > >
> > > > > The implementation of
> > > > >
> > > > > KIP-698: Add Explicit User Initialization of Broker-side State to
> > Kafka
> > > > > Streams
> > > > >
> > > > > will not be ready for 3.0, so you can remove it from the list.
> > > > >
> > > > > Best,
> > > > > Bruno
> > > > >
> > > > > On 15.06.21 07:33, Konstantine Karantasis wrote:
> > > > > > Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and
> > to
> > > > the
> > > > > > release plan of course.
> > > > > > Thanks for catching this Israel.
> > > > > >
> > > > > > Best,
> > > > > > Konstantine
> > > > > >
> > > > > > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo <
> israele...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > >> Konstantine,
> > > > > >>
> > > > > >> One of mine is missing from this list
> > > > > >>
> > > > > >> KIP-633: Drop 24 hour default of grace period in Streams
> > > > > >> Please could you include it?
> > > > > >>
> > > > > >> Voting has already concluded a long time ago
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
> > > > > >>  wrote:
> > > > > >>
> > > > > >>> Hi all.
> > > > > >>>
> > > > > >>> KIP Freeze for the next major release of Apache Kafka was
> reached
> > > > last
> > > > > >>> week.
> > > > > >>>
> > > > > >>> As of now, 36 KIPs have concluded their voting process and have
> > been
> > > > > >>> adopted.
> > > > > >>> These KIPs are targeting 3.0 (unless it's noted otherwise in
> the
> > > > > release
> > > > > >>> plan) and their inclusion as new features will be finalized
> right
> > > > after
> > > > > >>> Feature Freeze.
> > > > > >>>
> > > > > >>> At the high level, out of these 36 KIPs, 11 have been
> implemented
> > > > > already
> > > > > >>> and 25 are open or in progress.
> > > > > >>> Here is the full list of adopted KIPs:
> > > > > >>>
> > > > > >>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in
> > 3.0)
> > > > > >>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in
> 3.0)
> > > > > >>> KIP-746: Revise KRaft Metadata Records
> > > > > >>> KIP-745: Connect API to restart connector and tasks
> > > > > >>> KIP-744: Migrate TaskMetadata and ThreadMetadata to an
> interface
> > with
> > > > > >>> internal implementation
> > > > > >>> KIP-743: Remove config value 0.10.0-2.4 of Streams built-in
> > metrics
> > > > > >> version
> > > > > >>> config
> > > > > >>> KIP-741: Change default serde to be null
> > > > > >>> KIP-740: Clean up public API in TaskId and fix
> > TaskMetadata#taskId()
> > > > > >>> KIP-738: Removal of Connect's internal converter properties
> > > > > >>> KIP-734: Improve AdminClient.listOffsets to return timestamp
> and
> > > > offset
> > > > > >> for
> > > > > >>> the record with the largest timestamp
> > > > > >>> KIP-733: Change Kafka Streams default replication factor config
> > > > > >>> KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
> > > > > >>> KIP-730: Producer ID generation in KRaft mode
> > > > > >>> KIP-726: Make the "cooperative-sticky, range" as the default
> > assignor
> > > > > >>> KIP-725: Streamlining configurations for WindowedSerializer and
> > > > > >>> WindowedDeserializer.
> > > > > >>> KIP-724: Drop support for message formats v0 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for the update Colin.
They are now both in the release plan.

Best,
Konstantine

On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe  wrote:

> Hi Konstantine,
>
> Can you please add two KIPs to the 3.0 release plan wiki page?
>
> I'm thinking of:
> KIP-630: Kafka Raft Snapshots
> KIP-746: Revise KRaft Metadata Records
>
> These are marked as 3.0 on the KIP page but I guess we don't have them on
> the page yet.
>
> Many thanks.
> Colin
>
>
> On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
> > Hi there,
> >
> > As the feature freeze date is approaching, I just wanted to kindly ask
> for
> > some reviews on the already submitted PR (
> > https://github.com/apache/kafka/pull/10840) that implements the approved
> > KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has been
> > ready for review for 2 weeks, and I simply want to make sure there is
> > enough time to address any possible changes that might be requested.
> >
> > Thanks in advance and sorry for any inconvenience caused,
> > --
> > Josep
> > On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
> >  wrote:
> >
> > > Thanks for the update Bruno.
> > > I've moved KIP-698 to the list of postponed KIPs in the plan.
> > >
> > > Konstantine
> > >
> > > On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna 
> wrote:
> > >
> > > > Hi Konstantine,
> > > >
> > > > The implementation of
> > > >
> > > > KIP-698: Add Explicit User Initialization of Broker-side State to
> Kafka
> > > > Streams
> > > >
> > > > will not be ready for 3.0, so you can remove it from the list.
> > > >
> > > > Best,
> > > > Bruno
> > > >
> > > > On 15.06.21 07:33, Konstantine Karantasis wrote:
> > > > > Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and
> to
> > > the
> > > > > release plan of course.
> > > > > Thanks for catching this Israel.
> > > > >
> > > > > Best,
> > > > > Konstantine
> > > > >
> > > > > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo 
> > > > wrote:
> > > > >
> > > > >> Konstantine,
> > > > >>
> > > > >> One of mine is missing from this list
> > > > >>
> > > > >> KIP-633: Drop 24 hour default of grace period in Streams
> > > > >> Please could you include it?
> > > > >>
> > > > >> Voting has already concluded a long time ago
> > > > >>
> > > > >>
> > > > >>
> > > > >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
> > > > >>  wrote:
> > > > >>
> > > > >>> Hi all.
> > > > >>>
> > > > >>> KIP Freeze for the next major release of Apache Kafka was reached
> > > last
> > > > >>> week.
> > > > >>>
> > > > >>> As of now, 36 KIPs have concluded their voting process and have
> been
> > > > >>> adopted.
> > > > >>> These KIPs are targeting 3.0 (unless it's noted otherwise in the
> > > > release
> > > > >>> plan) and their inclusion as new features will be finalized right
> > > after
> > > > >>> Feature Freeze.
> > > > >>>
> > > > >>> At the high level, out of these 36 KIPs, 11 have been implemented
> > > > already
> > > > >>> and 25 are open or in progress.
> > > > >>> Here is the full list of adopted KIPs:
> > > > >>>
> > > > >>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in
> 3.0)
> > > > >>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
> > > > >>> KIP-746: Revise KRaft Metadata Records
> > > > >>> KIP-745: Connect API to restart connector and tasks
> > > > >>> KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface
> with
> > > > >>> internal implementation
> > > > >>> KIP-743: Remove config value 0.10.0-2.4 of Streams built-in
> metrics
> > > > >> version
> > > > >>> config
> > > > >>> KIP-741: Change default serde to be null
> > > > >>> KIP-740: Clean up public API in TaskId and fix
> TaskMetadata#taskId()
> > > > >>> KIP-738: Removal of Connect's internal converter properties
> > > > >>> KIP-734: Improve AdminClient.listOffsets to return timestamp and
> > > offset
> > > > >> for
> > > > >>> the record with the largest timestamp
> > > > >>> KIP-733: Change Kafka Streams default replication factor config
> > > > >>> KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
> > > > >>> KIP-730: Producer ID generation in KRaft mode
> > > > >>> KIP-726: Make the "cooperative-sticky, range" as the default
> assignor
> > > > >>> KIP-725: Streamlining configurations for WindowedSerializer and
> > > > >>> WindowedDeserializer.
> > > > >>> KIP-724: Drop support for message formats v0 and v1
> > > > >>> KIP-722: Enable connector client overrides by default
> > > > >>> KIP-721: Enable connector log contexts in Connect Log4j
> configuration
> > > > >>> KIP-720: Deprecate MirrorMaker v1
> > > > >>> KIP-716: Allow configuring the location of the offset-syncs topic
> > > with
> > > > >>> MirrorMaker2
> > > > >>> KIP-715: Expose Committed offset in streams
> > > > >>> KIP-709: Extend OffsetFetch requests to accept multiple group
> ids.
> > > > >>> KIP-708: Rack awareness for Kafka Streams
> > > > >>> KIP-707: The future of KafkaFuture
> > > > >>> KIP-699: Update FindCoordinator to resolve multiple 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Colin McCabe]

Hi Konstantine,

Can you please add two KIPs to the 3.0 release plan wiki page?

I'm thinking of:
KIP-630: Kafka Raft Snapshots
KIP-746: Revise KRaft Metadata Records

These are marked as 3.0 on the KIP page but I guess we don't have them on the 
page yet.

Many thanks.
Colin


On Tue, Jun 22, 2021, at 06:29, Josep Prat wrote:
> Hi there,
> 
> As the feature freeze date is approaching, I just wanted to kindly ask for
> some reviews on the already submitted PR (
> https://github.com/apache/kafka/pull/10840) that implements the approved
> KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has been
> ready for review for 2 weeks, and I simply want to make sure there is
> enough time to address any possible changes that might be requested.
> 
> Thanks in advance and sorry for any inconvenience caused,
> --
> Josep
> On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
>  wrote:
> 
> > Thanks for the update Bruno.
> > I've moved KIP-698 to the list of postponed KIPs in the plan.
> >
> > Konstantine
> >
> > On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna  wrote:
> >
> > > Hi Konstantine,
> > >
> > > The implementation of
> > >
> > > KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
> > > Streams
> > >
> > > will not be ready for 3.0, so you can remove it from the list.
> > >
> > > Best,
> > > Bruno
> > >
> > > On 15.06.21 07:33, Konstantine Karantasis wrote:
> > > > Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and to
> > the
> > > > release plan of course.
> > > > Thanks for catching this Israel.
> > > >
> > > > Best,
> > > > Konstantine
> > > >
> > > > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo 
> > > wrote:
> > > >
> > > >> Konstantine,
> > > >>
> > > >> One of mine is missing from this list
> > > >>
> > > >> KIP-633: Drop 24 hour default of grace period in Streams
> > > >> Please could you include it?
> > > >>
> > > >> Voting has already concluded a long time ago
> > > >>
> > > >>
> > > >>
> > > >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
> > > >>  wrote:
> > > >>
> > > >>> Hi all.
> > > >>>
> > > >>> KIP Freeze for the next major release of Apache Kafka was reached
> > last
> > > >>> week.
> > > >>>
> > > >>> As of now, 36 KIPs have concluded their voting process and have been
> > > >>> adopted.
> > > >>> These KIPs are targeting 3.0 (unless it's noted otherwise in the
> > > release
> > > >>> plan) and their inclusion as new features will be finalized right
> > after
> > > >>> Feature Freeze.
> > > >>>
> > > >>> At the high level, out of these 36 KIPs, 11 have been implemented
> > > already
> > > >>> and 25 are open or in progress.
> > > >>> Here is the full list of adopted KIPs:
> > > >>>
> > > >>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)
> > > >>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
> > > >>> KIP-746: Revise KRaft Metadata Records
> > > >>> KIP-745: Connect API to restart connector and tasks
> > > >>> KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with
> > > >>> internal implementation
> > > >>> KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics
> > > >> version
> > > >>> config
> > > >>> KIP-741: Change default serde to be null
> > > >>> KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()
> > > >>> KIP-738: Removal of Connect's internal converter properties
> > > >>> KIP-734: Improve AdminClient.listOffsets to return timestamp and
> > offset
> > > >> for
> > > >>> the record with the largest timestamp
> > > >>> KIP-733: Change Kafka Streams default replication factor config
> > > >>> KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
> > > >>> KIP-730: Producer ID generation in KRaft mode
> > > >>> KIP-726: Make the "cooperative-sticky, range" as the default assignor
> > > >>> KIP-725: Streamlining configurations for WindowedSerializer and
> > > >>> WindowedDeserializer.
> > > >>> KIP-724: Drop support for message formats v0 and v1
> > > >>> KIP-722: Enable connector client overrides by default
> > > >>> KIP-721: Enable connector log contexts in Connect Log4j configuration
> > > >>> KIP-720: Deprecate MirrorMaker v1
> > > >>> KIP-716: Allow configuring the location of the offset-syncs topic
> > with
> > > >>> MirrorMaker2
> > > >>> KIP-715: Expose Committed offset in streams
> > > >>> KIP-709: Extend OffsetFetch requests to accept multiple group ids.
> > > >>> KIP-708: Rack awareness for Kafka Streams
> > > >>> KIP-707: The future of KafkaFuture
> > > >>> KIP-699: Update FindCoordinator to resolve multiple Coordinators at a
> > > >> time
> > > >>> KIP-698: Add Explicit User Initialization of Broker-side State to
> > Kafka
> > > >>> Streams
> > > >>> KIP-695: Further Improve Kafka Streams Timestamp Synchronization
> > > >>> KIP-691: Enhance Transactional Producer Exception Handling
> > > >>> KIP-679: Producer will enable the strongest delivery guarantee by
> > > default
> > > >>> KIP-666: Add Instant-based methods 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Josep Prat]

Hi there,

As the feature freeze date is approaching, I just wanted to kindly ask for
some reviews on the already submitted PR (
https://github.com/apache/kafka/pull/10840) that implements the approved
KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has been
ready for review for 2 weeks, and I simply want to make sure there is
enough time to address any possible changes that might be requested.

Thanks in advance and sorry for any inconvenience caused,
--
Josep
On Mon, Jun 21, 2021 at 11:54 PM Konstantine Karantasis
 wrote:

> Thanks for the update Bruno.
> I've moved KIP-698 to the list of postponed KIPs in the plan.
>
> Konstantine
>
> On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna  wrote:
>
> > Hi Konstantine,
> >
> > The implementation of
> >
> > KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
> > Streams
> >
> > will not be ready for 3.0, so you can remove it from the list.
> >
> > Best,
> > Bruno
> >
> > On 15.06.21 07:33, Konstantine Karantasis wrote:
> > > Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and to
> the
> > > release plan of course.
> > > Thanks for catching this Israel.
> > >
> > > Best,
> > > Konstantine
> > >
> > > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo 
> > wrote:
> > >
> > >> Konstantine,
> > >>
> > >> One of mine is missing from this list
> > >>
> > >> KIP-633: Drop 24 hour default of grace period in Streams
> > >> Please could you include it?
> > >>
> > >> Voting has already concluded a long time ago
> > >>
> > >>
> > >>
> > >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
> > >>  wrote:
> > >>
> > >>> Hi all.
> > >>>
> > >>> KIP Freeze for the next major release of Apache Kafka was reached
> last
> > >>> week.
> > >>>
> > >>> As of now, 36 KIPs have concluded their voting process and have been
> > >>> adopted.
> > >>> These KIPs are targeting 3.0 (unless it's noted otherwise in the
> > release
> > >>> plan) and their inclusion as new features will be finalized right
> after
> > >>> Feature Freeze.
> > >>>
> > >>> At the high level, out of these 36 KIPs, 11 have been implemented
> > already
> > >>> and 25 are open or in progress.
> > >>> Here is the full list of adopted KIPs:
> > >>>
> > >>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)
> > >>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
> > >>> KIP-746: Revise KRaft Metadata Records
> > >>> KIP-745: Connect API to restart connector and tasks
> > >>> KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with
> > >>> internal implementation
> > >>> KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics
> > >> version
> > >>> config
> > >>> KIP-741: Change default serde to be null
> > >>> KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()
> > >>> KIP-738: Removal of Connect's internal converter properties
> > >>> KIP-734: Improve AdminClient.listOffsets to return timestamp and
> offset
> > >> for
> > >>> the record with the largest timestamp
> > >>> KIP-733: Change Kafka Streams default replication factor config
> > >>> KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
> > >>> KIP-730: Producer ID generation in KRaft mode
> > >>> KIP-726: Make the "cooperative-sticky, range" as the default assignor
> > >>> KIP-725: Streamlining configurations for WindowedSerializer and
> > >>> WindowedDeserializer.
> > >>> KIP-724: Drop support for message formats v0 and v1
> > >>> KIP-722: Enable connector client overrides by default
> > >>> KIP-721: Enable connector log contexts in Connect Log4j configuration
> > >>> KIP-720: Deprecate MirrorMaker v1
> > >>> KIP-716: Allow configuring the location of the offset-syncs topic
> with
> > >>> MirrorMaker2
> > >>> KIP-715: Expose Committed offset in streams
> > >>> KIP-709: Extend OffsetFetch requests to accept multiple group ids.
> > >>> KIP-708: Rack awareness for Kafka Streams
> > >>> KIP-707: The future of KafkaFuture
> > >>> KIP-699: Update FindCoordinator to resolve multiple Coordinators at a
> > >> time
> > >>> KIP-698: Add Explicit User Initialization of Broker-side State to
> Kafka
> > >>> Streams
> > >>> KIP-695: Further Improve Kafka Streams Timestamp Synchronization
> > >>> KIP-691: Enhance Transactional Producer Exception Handling
> > >>> KIP-679: Producer will enable the strongest delivery guarantee by
> > default
> > >>> KIP-666: Add Instant-based methods to ReadOnlySessionStore
> > >>> KIP-653: Upgrade log4j to log4j2
> > >>> KIP-623: Add "internal-topics" option to streams application reset
> tool
> > >>> KIP-622: Add currentSystemTimeMs and currentStreamTimeMs to
> > >>> ProcessorContext
> > >>> KIP-466: Add support for List serialization and deserialization
> > >>> KIP-405: Kafka Tiered Storage
> > >>> KIP-390: Support Compression Level
> > >>>
> > >>> If you notice that a KIP is missing from the list above and should be
> > >> part
> > >>> of the release plan for 3.0, please reply below.
> > >>> The single source of 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks for the update Bruno.
I've moved KIP-698 to the list of postponed KIPs in the plan.

Konstantine

On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna  wrote:

> Hi Konstantine,
>
> The implementation of
>
> KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
> Streams
>
> will not be ready for 3.0, so you can remove it from the list.
>
> Best,
> Bruno
>
> On 15.06.21 07:33, Konstantine Karantasis wrote:
> > Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and to the
> > release plan of course.
> > Thanks for catching this Israel.
> >
> > Best,
> > Konstantine
> >
> > On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo 
> wrote:
> >
> >> Konstantine,
> >>
> >> One of mine is missing from this list
> >>
> >> KIP-633: Drop 24 hour default of grace period in Streams
> >> Please could you include it?
> >>
> >> Voting has already concluded a long time ago
> >>
> >>
> >>
> >> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
> >>  wrote:
> >>
> >>> Hi all.
> >>>
> >>> KIP Freeze for the next major release of Apache Kafka was reached last
> >>> week.
> >>>
> >>> As of now, 36 KIPs have concluded their voting process and have been
> >>> adopted.
> >>> These KIPs are targeting 3.0 (unless it's noted otherwise in the
> release
> >>> plan) and their inclusion as new features will be finalized right after
> >>> Feature Freeze.
> >>>
> >>> At the high level, out of these 36 KIPs, 11 have been implemented
> already
> >>> and 25 are open or in progress.
> >>> Here is the full list of adopted KIPs:
> >>>
> >>> KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)
> >>> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
> >>> KIP-746: Revise KRaft Metadata Records
> >>> KIP-745: Connect API to restart connector and tasks
> >>> KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with
> >>> internal implementation
> >>> KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics
> >> version
> >>> config
> >>> KIP-741: Change default serde to be null
> >>> KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()
> >>> KIP-738: Removal of Connect's internal converter properties
> >>> KIP-734: Improve AdminClient.listOffsets to return timestamp and offset
> >> for
> >>> the record with the largest timestamp
> >>> KIP-733: Change Kafka Streams default replication factor config
> >>> KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
> >>> KIP-730: Producer ID generation in KRaft mode
> >>> KIP-726: Make the "cooperative-sticky, range" as the default assignor
> >>> KIP-725: Streamlining configurations for WindowedSerializer and
> >>> WindowedDeserializer.
> >>> KIP-724: Drop support for message formats v0 and v1
> >>> KIP-722: Enable connector client overrides by default
> >>> KIP-721: Enable connector log contexts in Connect Log4j configuration
> >>> KIP-720: Deprecate MirrorMaker v1
> >>> KIP-716: Allow configuring the location of the offset-syncs topic with
> >>> MirrorMaker2
> >>> KIP-715: Expose Committed offset in streams
> >>> KIP-709: Extend OffsetFetch requests to accept multiple group ids.
> >>> KIP-708: Rack awareness for Kafka Streams
> >>> KIP-707: The future of KafkaFuture
> >>> KIP-699: Update FindCoordinator to resolve multiple Coordinators at a
> >> time
> >>> KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
> >>> Streams
> >>> KIP-695: Further Improve Kafka Streams Timestamp Synchronization
> >>> KIP-691: Enhance Transactional Producer Exception Handling
> >>> KIP-679: Producer will enable the strongest delivery guarantee by
> default
> >>> KIP-666: Add Instant-based methods to ReadOnlySessionStore
> >>> KIP-653: Upgrade log4j to log4j2
> >>> KIP-623: Add "internal-topics" option to streams application reset tool
> >>> KIP-622: Add currentSystemTimeMs and currentStreamTimeMs to
> >>> ProcessorContext
> >>> KIP-466: Add support for List serialization and deserialization
> >>> KIP-405: Kafka Tiered Storage
> >>> KIP-390: Support Compression Level
> >>>
> >>> If you notice that a KIP is missing from the list above and should be
> >> part
> >>> of the release plan for 3.0, please reply below.
> >>> The single source of truth remains the official release plan for 3.0,
> >> which
> >>> you may read at any time here:
> >>>
> >>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> >>>
> >>> Kind reminder that for all the adopted KIPs any required changes to the
> >>> documentation are also part of their respective feature.
> >>>
> >>> For the KIPs that are still in progress, please work closely with your
> >>> reviewers to make sure that the features are stable and land on time
> for
> >>> Feature Freeze.
> >>>
> >>> The next milestone for the Apache Kafka 3.0 release is Feature Freeze
> on
> >>> June 30th, 2021.
> >>>
> >>> Best regards,
> >>> Konstantine
> >>>
> >>> On Fri, Jun 4, 2021 at 3:47 PM Konstantine Karantasis <
> >>> konstant...@confluent.io> wrote:
> >>>
> 
> 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Bruno Cadonna]

Hi Konstantine,

The implementation of

KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
Streams

will not be ready for 3.0, so you can remove it from the list.

Best,
Bruno

On 15.06.21 07:33, Konstantine Karantasis wrote:

Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and to the
release plan of course.
Thanks for catching this Israel.

Best,
Konstantine

On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo  wrote:


Konstantine,

One of mine is missing from this list

KIP-633: Drop 24 hour default of grace period in Streams
Please could you include it?

Voting has already concluded a long time ago



On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
 wrote:


Hi all.

KIP Freeze for the next major release of Apache Kafka was reached last
week.

As of now, 36 KIPs have concluded their voting process and have been
adopted.
These KIPs are targeting 3.0 (unless it's noted otherwise in the release
plan) and their inclusion as new features will be finalized right after
Feature Freeze.

At the high level, out of these 36 KIPs, 11 have been implemented already
and 25 are open or in progress.
Here is the full list of adopted KIPs:

KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)
KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
KIP-746: Revise KRaft Metadata Records
KIP-745: Connect API to restart connector and tasks
KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with
internal implementation
KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics

version

config
KIP-741: Change default serde to be null
KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()
KIP-738: Removal of Connect's internal converter properties
KIP-734: Improve AdminClient.listOffsets to return timestamp and offset

for

the record with the largest timestamp
KIP-733: Change Kafka Streams default replication factor config
KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
KIP-730: Producer ID generation in KRaft mode
KIP-726: Make the "cooperative-sticky, range" as the default assignor
KIP-725: Streamlining configurations for WindowedSerializer and
WindowedDeserializer.
KIP-724: Drop support for message formats v0 and v1
KIP-722: Enable connector client overrides by default
KIP-721: Enable connector log contexts in Connect Log4j configuration
KIP-720: Deprecate MirrorMaker v1
KIP-716: Allow configuring the location of the offset-syncs topic with
MirrorMaker2
KIP-715: Expose Committed offset in streams
KIP-709: Extend OffsetFetch requests to accept multiple group ids.
KIP-708: Rack awareness for Kafka Streams
KIP-707: The future of KafkaFuture
KIP-699: Update FindCoordinator to resolve multiple Coordinators at a

time

KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
Streams
KIP-695: Further Improve Kafka Streams Timestamp Synchronization
KIP-691: Enhance Transactional Producer Exception Handling
KIP-679: Producer will enable the strongest delivery guarantee by default
KIP-666: Add Instant-based methods to ReadOnlySessionStore
KIP-653: Upgrade log4j to log4j2
KIP-623: Add "internal-topics" option to streams application reset tool
KIP-622: Add currentSystemTimeMs and currentStreamTimeMs to
ProcessorContext
KIP-466: Add support for List serialization and deserialization
KIP-405: Kafka Tiered Storage
KIP-390: Support Compression Level

If you notice that a KIP is missing from the list above and should be

part

of the release plan for 3.0, please reply below.
The single source of truth remains the official release plan for 3.0,

which

you may read at any time here:

https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0

Kind reminder that for all the adopted KIPs any required changes to the
documentation are also part of their respective feature.

For the KIPs that are still in progress, please work closely with your
reviewers to make sure that the features are stable and land on time for
Feature Freeze.

The next milestone for the Apache Kafka 3.0 release is Feature Freeze on
June 30th, 2021.

Best regards,
Konstantine

On Fri, Jun 4, 2021 at 3:47 PM Konstantine Karantasis <
konstant...@confluent.io> wrote:



Hi all,

Just a quick reminder that KIP Freeze is next Wednesday, June 9th.
A vote thread needs to be open for at least 72 hours, so to everyone

that

is working hard on proposals targeting 3.0.0, please make sure that

your

[VOTE] threads are started on time.

Best,
Konstantine


On Wed, May 26, 2021 at 8:10 PM Israel Ekpo 

wrote:



+1 on the new schedule.

On Wed, May 26, 2021 at 8:14 PM Sophie Blee-Goldman
 wrote:


Ah ok, thanks Konstantine. I won't bug you about every new KIP that

comes

in between now and KIP Freeze :P

+1 on the scheduling changes as well

On Wed, May 26, 2021 at 4:00 PM David Arthur 

wrote:



The new schedule looks good to me, +1

On Wed, May 26, 2021 at 6:29 PM Ismael Juma 

wrote:



Thanks Konstantine, +1 from me.

Ismael

On Wed, May 26, 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and to the
release plan of course.
Thanks for catching this Israel.

Best,
Konstantine

On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo  wrote:

> Konstantine,
>
> One of mine is missing from this list
>
> KIP-633: Drop 24 hour default of grace period in Streams
> Please could you include it?
>
> Voting has already concluded a long time ago
>
>
>
> On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
>  wrote:
>
> > Hi all.
> >
> > KIP Freeze for the next major release of Apache Kafka was reached last
> > week.
> >
> > As of now, 36 KIPs have concluded their voting process and have been
> > adopted.
> > These KIPs are targeting 3.0 (unless it's noted otherwise in the release
> > plan) and their inclusion as new features will be finalized right after
> > Feature Freeze.
> >
> > At the high level, out of these 36 KIPs, 11 have been implemented already
> > and 25 are open or in progress.
> > Here is the full list of adopted KIPs:
> >
> > KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)
> > KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
> > KIP-746: Revise KRaft Metadata Records
> > KIP-745: Connect API to restart connector and tasks
> > KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with
> > internal implementation
> > KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics
> version
> > config
> > KIP-741: Change default serde to be null
> > KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()
> > KIP-738: Removal of Connect's internal converter properties
> > KIP-734: Improve AdminClient.listOffsets to return timestamp and offset
> for
> > the record with the largest timestamp
> > KIP-733: Change Kafka Streams default replication factor config
> > KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
> > KIP-730: Producer ID generation in KRaft mode
> > KIP-726: Make the "cooperative-sticky, range" as the default assignor
> > KIP-725: Streamlining configurations for WindowedSerializer and
> > WindowedDeserializer.
> > KIP-724: Drop support for message formats v0 and v1
> > KIP-722: Enable connector client overrides by default
> > KIP-721: Enable connector log contexts in Connect Log4j configuration
> > KIP-720: Deprecate MirrorMaker v1
> > KIP-716: Allow configuring the location of the offset-syncs topic with
> > MirrorMaker2
> > KIP-715: Expose Committed offset in streams
> > KIP-709: Extend OffsetFetch requests to accept multiple group ids.
> > KIP-708: Rack awareness for Kafka Streams
> > KIP-707: The future of KafkaFuture
> > KIP-699: Update FindCoordinator to resolve multiple Coordinators at a
> time
> > KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
> > Streams
> > KIP-695: Further Improve Kafka Streams Timestamp Synchronization
> > KIP-691: Enhance Transactional Producer Exception Handling
> > KIP-679: Producer will enable the strongest delivery guarantee by default
> > KIP-666: Add Instant-based methods to ReadOnlySessionStore
> > KIP-653: Upgrade log4j to log4j2
> > KIP-623: Add "internal-topics" option to streams application reset tool
> > KIP-622: Add currentSystemTimeMs and currentStreamTimeMs to
> > ProcessorContext
> > KIP-466: Add support for List serialization and deserialization
> > KIP-405: Kafka Tiered Storage
> > KIP-390: Support Compression Level
> >
> > If you notice that a KIP is missing from the list above and should be
> part
> > of the release plan for 3.0, please reply below.
> > The single source of truth remains the official release plan for 3.0,
> which
> > you may read at any time here:
> >
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
> >
> > Kind reminder that for all the adopted KIPs any required changes to the
> > documentation are also part of their respective feature.
> >
> > For the KIPs that are still in progress, please work closely with your
> > reviewers to make sure that the features are stable and land on time for
> > Feature Freeze.
> >
> > The next milestone for the Apache Kafka 3.0 release is Feature Freeze on
> > June 30th, 2021.
> >
> > Best regards,
> > Konstantine
> >
> > On Fri, Jun 4, 2021 at 3:47 PM Konstantine Karantasis <
> > konstant...@confluent.io> wrote:
> >
> > >
> > > Hi all,
> > >
> > > Just a quick reminder that KIP Freeze is next Wednesday, June 9th.
> > > A vote thread needs to be open for at least 72 hours, so to everyone
> that
> > > is working hard on proposals targeting 3.0.0, please make sure that
> your
> > > [VOTE] threads are started on time.
> > >
> > > Best,
> > > Konstantine
> > >
> > >
> > > On Wed, May 26, 2021 at 8:10 PM Israel Ekpo 
> > wrote:
> > >
> > >> +1 on the new schedule.
> > >>
> > >> On Wed, May 26, 2021 at 8:14 PM Sophie Blee-Goldman
> > >>  wrote:
> > >>
> > >> > Ah ok, thanks Konstantine. I won't bug you about every new KIP that
> > >> comes
> > >> > in between now and KIP Freeze :P
> > >> >
> > >> > +1 on the 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Israel Ekpo]

Konstantine,

One of mine is missing from this list

KIP-633: Drop 24 hour default of grace period in Streams
Please could you include it?

Voting has already concluded a long time ago



On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
 wrote:

> Hi all.
>
> KIP Freeze for the next major release of Apache Kafka was reached last
> week.
>
> As of now, 36 KIPs have concluded their voting process and have been
> adopted.
> These KIPs are targeting 3.0 (unless it's noted otherwise in the release
> plan) and their inclusion as new features will be finalized right after
> Feature Freeze.
>
> At the high level, out of these 36 KIPs, 11 have been implemented already
> and 25 are open or in progress.
> Here is the full list of adopted KIPs:
>
> KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)
> KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
> KIP-746: Revise KRaft Metadata Records
> KIP-745: Connect API to restart connector and tasks
> KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with
> internal implementation
> KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics version
> config
> KIP-741: Change default serde to be null
> KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()
> KIP-738: Removal of Connect's internal converter properties
> KIP-734: Improve AdminClient.listOffsets to return timestamp and offset for
> the record with the largest timestamp
> KIP-733: Change Kafka Streams default replication factor config
> KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
> KIP-730: Producer ID generation in KRaft mode
> KIP-726: Make the "cooperative-sticky, range" as the default assignor
> KIP-725: Streamlining configurations for WindowedSerializer and
> WindowedDeserializer.
> KIP-724: Drop support for message formats v0 and v1
> KIP-722: Enable connector client overrides by default
> KIP-721: Enable connector log contexts in Connect Log4j configuration
> KIP-720: Deprecate MirrorMaker v1
> KIP-716: Allow configuring the location of the offset-syncs topic with
> MirrorMaker2
> KIP-715: Expose Committed offset in streams
> KIP-709: Extend OffsetFetch requests to accept multiple group ids.
> KIP-708: Rack awareness for Kafka Streams
> KIP-707: The future of KafkaFuture
> KIP-699: Update FindCoordinator to resolve multiple Coordinators at a time
> KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
> Streams
> KIP-695: Further Improve Kafka Streams Timestamp Synchronization
> KIP-691: Enhance Transactional Producer Exception Handling
> KIP-679: Producer will enable the strongest delivery guarantee by default
> KIP-666: Add Instant-based methods to ReadOnlySessionStore
> KIP-653: Upgrade log4j to log4j2
> KIP-623: Add "internal-topics" option to streams application reset tool
> KIP-622: Add currentSystemTimeMs and currentStreamTimeMs to
> ProcessorContext
> KIP-466: Add support for List serialization and deserialization
> KIP-405: Kafka Tiered Storage
> KIP-390: Support Compression Level
>
> If you notice that a KIP is missing from the list above and should be part
> of the release plan for 3.0, please reply below.
> The single source of truth remains the official release plan for 3.0, which
> you may read at any time here:
>
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
>
> Kind reminder that for all the adopted KIPs any required changes to the
> documentation are also part of their respective feature.
>
> For the KIPs that are still in progress, please work closely with your
> reviewers to make sure that the features are stable and land on time for
> Feature Freeze.
>
> The next milestone for the Apache Kafka 3.0 release is Feature Freeze on
> June 30th, 2021.
>
> Best regards,
> Konstantine
>
> On Fri, Jun 4, 2021 at 3:47 PM Konstantine Karantasis <
> konstant...@confluent.io> wrote:
>
> >
> > Hi all,
> >
> > Just a quick reminder that KIP Freeze is next Wednesday, June 9th.
> > A vote thread needs to be open for at least 72 hours, so to everyone that
> > is working hard on proposals targeting 3.0.0, please make sure that your
> > [VOTE] threads are started on time.
> >
> > Best,
> > Konstantine
> >
> >
> > On Wed, May 26, 2021 at 8:10 PM Israel Ekpo 
> wrote:
> >
> >> +1 on the new schedule.
> >>
> >> On Wed, May 26, 2021 at 8:14 PM Sophie Blee-Goldman
> >>  wrote:
> >>
> >> > Ah ok, thanks Konstantine. I won't bug you about every new KIP that
> >> comes
> >> > in between now and KIP Freeze :P
> >> >
> >> > +1 on the scheduling changes as well
> >> >
> >> > On Wed, May 26, 2021 at 4:00 PM David Arthur 
> wrote:
> >> >
> >> > > The new schedule looks good to me, +1
> >> > >
> >> > > On Wed, May 26, 2021 at 6:29 PM Ismael Juma 
> >> wrote:
> >> > >
> >> > > > Thanks Konstantine, +1 from me.
> >> > > >
> >> > > > Ismael
> >> > > >
> >> > > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> >> > > >  wrote:
> >> > > >
> >> > > > > Hi all,
> >> > > > >
> >> > > 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi all.

KIP Freeze for the next major release of Apache Kafka was reached last
week.

As of now, 36 KIPs have concluded their voting process and have been
adopted.
These KIPs are targeting 3.0 (unless it's noted otherwise in the release
plan) and their inclusion as new features will be finalized right after
Feature Freeze.

At the high level, out of these 36 KIPs, 11 have been implemented already
and 25 are open or in progress.
Here is the full list of adopted KIPs:

KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)
KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)
KIP-746: Revise KRaft Metadata Records
KIP-745: Connect API to restart connector and tasks
KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface with
internal implementation
KIP-743: Remove config value 0.10.0-2.4 of Streams built-in metrics version
config
KIP-741: Change default serde to be null
KIP-740: Clean up public API in TaskId and fix TaskMetadata#taskId()
KIP-738: Removal of Connect's internal converter properties
KIP-734: Improve AdminClient.listOffsets to return timestamp and offset for
the record with the largest timestamp
KIP-733: Change Kafka Streams default replication factor config
KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
KIP-730: Producer ID generation in KRaft mode
KIP-726: Make the "cooperative-sticky, range" as the default assignor
KIP-725: Streamlining configurations for WindowedSerializer and
WindowedDeserializer.
KIP-724: Drop support for message formats v0 and v1
KIP-722: Enable connector client overrides by default
KIP-721: Enable connector log contexts in Connect Log4j configuration
KIP-720: Deprecate MirrorMaker v1
KIP-716: Allow configuring the location of the offset-syncs topic with
MirrorMaker2
KIP-715: Expose Committed offset in streams
KIP-709: Extend OffsetFetch requests to accept multiple group ids.
KIP-708: Rack awareness for Kafka Streams
KIP-707: The future of KafkaFuture
KIP-699: Update FindCoordinator to resolve multiple Coordinators at a time
KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
Streams
KIP-695: Further Improve Kafka Streams Timestamp Synchronization
KIP-691: Enhance Transactional Producer Exception Handling
KIP-679: Producer will enable the strongest delivery guarantee by default
KIP-666: Add Instant-based methods to ReadOnlySessionStore
KIP-653: Upgrade log4j to log4j2
KIP-623: Add "internal-topics" option to streams application reset tool
KIP-622: Add currentSystemTimeMs and currentStreamTimeMs to ProcessorContext
KIP-466: Add support for List serialization and deserialization
KIP-405: Kafka Tiered Storage
KIP-390: Support Compression Level

If you notice that a KIP is missing from the list above and should be part
of the release plan for 3.0, please reply below.
The single source of truth remains the official release plan for 3.0, which
you may read at any time here:

https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0

Kind reminder that for all the adopted KIPs any required changes to the
documentation are also part of their respective feature.

For the KIPs that are still in progress, please work closely with your
reviewers to make sure that the features are stable and land on time for
Feature Freeze.

The next milestone for the Apache Kafka 3.0 release is Feature Freeze on
June 30th, 2021.

Best regards,
Konstantine

On Fri, Jun 4, 2021 at 3:47 PM Konstantine Karantasis <
konstant...@confluent.io> wrote:

>
> Hi all,
>
> Just a quick reminder that KIP Freeze is next Wednesday, June 9th.
> A vote thread needs to be open for at least 72 hours, so to everyone that
> is working hard on proposals targeting 3.0.0, please make sure that your
> [VOTE] threads are started on time.
>
> Best,
> Konstantine
>
>
> On Wed, May 26, 2021 at 8:10 PM Israel Ekpo  wrote:
>
>> +1 on the new schedule.
>>
>> On Wed, May 26, 2021 at 8:14 PM Sophie Blee-Goldman
>>  wrote:
>>
>> > Ah ok, thanks Konstantine. I won't bug you about every new KIP that
>> comes
>> > in between now and KIP Freeze :P
>> >
>> > +1 on the scheduling changes as well
>> >
>> > On Wed, May 26, 2021 at 4:00 PM David Arthur  wrote:
>> >
>> > > The new schedule looks good to me, +1
>> > >
>> > > On Wed, May 26, 2021 at 6:29 PM Ismael Juma 
>> wrote:
>> > >
>> > > > Thanks Konstantine, +1 from me.
>> > > >
>> > > > Ismael
>> > > >
>> > > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
>> > > >  wrote:
>> > > >
>> > > > > Hi all,
>> > > > >
>> > > > > Please find below the updated release plan for the Apache Kafka
>> 3.0.0
>> > > > > release.
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>> > > > >
>> > > > > New suggested dates for the release are as follows:
>> > > > >
>> > > > > KIP Freeze is 09 June 2021 (same date as in the initial plan)
>> > > > > Feature Freeze is 30 June 2021 (new date, extended by two weeks)
>> > > > > Code Freeze is 14 July 2021 

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Hi all,

Just a quick reminder that KIP Freeze is next Wednesday, June 9th.
A vote thread needs to be open for at least 72 hours, so to everyone that
is working hard on proposals targeting 3.0.0, please make sure that your
[VOTE] threads are started on time.

Best,
Konstantine


On Wed, May 26, 2021 at 8:10 PM Israel Ekpo  wrote:

> +1 on the new schedule.
>
> On Wed, May 26, 2021 at 8:14 PM Sophie Blee-Goldman
>  wrote:
>
> > Ah ok, thanks Konstantine. I won't bug you about every new KIP that comes
> > in between now and KIP Freeze :P
> >
> > +1 on the scheduling changes as well
> >
> > On Wed, May 26, 2021 at 4:00 PM David Arthur  wrote:
> >
> > > The new schedule looks good to me, +1
> > >
> > > On Wed, May 26, 2021 at 6:29 PM Ismael Juma  wrote:
> > >
> > > > Thanks Konstantine, +1 from me.
> > > >
> > > > Ismael
> > > >
> > > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> > > >  wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > Please find below the updated release plan for the Apache Kafka
> 3.0.0
> > > > > release.
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > > > >
> > > > > New suggested dates for the release are as follows:
> > > > >
> > > > > KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > > > > Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > > > > Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > > > >
> > > > > At least two weeks of stabilization will follow Code Freeze.
> > > > >
> > > > > The release plan is up to date and currently includes all the
> > approved
> > > > KIPs
> > > > > that are targeting 3.0.0.
> > > > >
> > > > > Please let me know if you have any objections with the recent
> > extension
> > > > of
> > > > > Feature Freeze and Code Freeze or any other concerns.
> > > > >
> > > > > Regards,
> > > > > Konstantine
> > > > >
> > > >
> > > --
> > > David Arthur
> > >
> >
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Israel Ekpo]

+1 on the new schedule.

On Wed, May 26, 2021 at 8:14 PM Sophie Blee-Goldman
 wrote:

> Ah ok, thanks Konstantine. I won't bug you about every new KIP that comes
> in between now and KIP Freeze :P
>
> +1 on the scheduling changes as well
>
> On Wed, May 26, 2021 at 4:00 PM David Arthur  wrote:
>
> > The new schedule looks good to me, +1
> >
> > On Wed, May 26, 2021 at 6:29 PM Ismael Juma  wrote:
> >
> > > Thanks Konstantine, +1 from me.
> > >
> > > Ismael
> > >
> > > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> > >  wrote:
> > >
> > > > Hi all,
> > > >
> > > > Please find below the updated release plan for the Apache Kafka 3.0.0
> > > > release.
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > > >
> > > > New suggested dates for the release are as follows:
> > > >
> > > > KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > > > Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > > > Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > > >
> > > > At least two weeks of stabilization will follow Code Freeze.
> > > >
> > > > The release plan is up to date and currently includes all the
> approved
> > > KIPs
> > > > that are targeting 3.0.0.
> > > >
> > > > Please let me know if you have any objections with the recent
> extension
> > > of
> > > > Feature Freeze and Code Freeze or any other concerns.
> > > >
> > > > Regards,
> > > > Konstantine
> > > >
> > >
> > --
> > David Arthur
> >
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Sophie Blee-Goldman]

Ah ok, thanks Konstantine. I won't bug you about every new KIP that comes
in between now and KIP Freeze :P

+1 on the scheduling changes as well

On Wed, May 26, 2021 at 4:00 PM David Arthur  wrote:

> The new schedule looks good to me, +1
>
> On Wed, May 26, 2021 at 6:29 PM Ismael Juma  wrote:
>
> > Thanks Konstantine, +1 from me.
> >
> > Ismael
> >
> > On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> >  wrote:
> >
> > > Hi all,
> > >
> > > Please find below the updated release plan for the Apache Kafka 3.0.0
> > > release.
> > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> > >
> > > New suggested dates for the release are as follows:
> > >
> > > KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > > Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > > Code Freeze is 14 July 2021 (new date, extended by two weeks)
> > >
> > > At least two weeks of stabilization will follow Code Freeze.
> > >
> > > The release plan is up to date and currently includes all the approved
> > KIPs
> > > that are targeting 3.0.0.
> > >
> > > Please let me know if you have any objections with the recent extension
> > of
> > > Feature Freeze and Code Freeze or any other concerns.
> > >
> > > Regards,
> > > Konstantine
> > >
> >
> --
> David Arthur
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[David Arthur]

The new schedule looks good to me, +1

On Wed, May 26, 2021 at 6:29 PM Ismael Juma  wrote:

> Thanks Konstantine, +1 from me.
>
> Ismael
>
> On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
>  wrote:
>
> > Hi all,
> >
> > Please find below the updated release plan for the Apache Kafka 3.0.0
> > release.
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> >
> > New suggested dates for the release are as follows:
> >
> > KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > Code Freeze is 14 July 2021 (new date, extended by two weeks)
> >
> > At least two weeks of stabilization will follow Code Freeze.
> >
> > The release plan is up to date and currently includes all the approved
> KIPs
> > that are targeting 3.0.0.
> >
> > Please let me know if you have any objections with the recent extension
> of
> > Feature Freeze and Code Freeze or any other concerns.
> >
> > Regards,
> > Konstantine
> >
>
-- 
David Arthur

Re: EXTERNAL: Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Guozhang Wang]

Hi Meiling,

Could you double check if the email sent is from non-sanboxed "
m...@rockwellautomation.com" instead of "m...@rockwellautomation.com.invalid"?
I believe the dev-unsubscr...@kafka.apache.org does work.

On Wed, May 26, 2021 at 3:32 PM Meiling He
 wrote:

> Can anyone instruct me how to unsubscribe from this mail list, please!!
> dev-unsubscr...@kafka.apache.org doesn’t work.
>
> 
> From: Ismael Juma 
> Sent: Wednesday, May 26, 2021 5:29:03 PM
> To: dev 
> Subject: EXTERNAL: Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new
> updated dates
>
> [Use caution with links & attachments]
>
>
>
> Thanks Konstantine, +1 from me.
>
> Ismael
>
> On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
>  wrote:
>
> > Hi all,
> >
> > Please find below the updated release plan for the Apache Kafka 3.0.0
> > release.
> >
> >
> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466__;!!JhrIYaSK6lFZ!-k0g-tIlibi6VoGNY2-ZLKPCfAz2RJ2ICdx4IA4TfulZQIp7Gx7rhD9f0KyCN4Gh2VwyHw$
> >
> > New suggested dates for the release are as follows:
> >
> > KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > Code Freeze is 14 July 2021 (new date, extended by two weeks)
> >
> > At least two weeks of stabilization will follow Code Freeze.
> >
> > The release plan is up to date and currently includes all the approved
> KIPs
> > that are targeting 3.0.0.
> >
> > Please let me know if you have any objections with the recent extension
> of
> > Feature Freeze and Code Freeze or any other concerns.
> >
> > Regards,
> > Konstantine
> >
>


-- 
-- Guozhang

Re: EXTERNAL: Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Meiling He]

Can anyone instruct me how to unsubscribe from this mail list, please!!  
dev-unsubscr...@kafka.apache.org doesn’t work.


From: Ismael Juma 
Sent: Wednesday, May 26, 2021 5:29:03 PM
To: dev 
Subject: EXTERNAL: Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new 
updated dates

[Use caution with links & attachments]



Thanks Konstantine, +1 from me.

Ismael

On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
 wrote:

> Hi all,
>
> Please find below the updated release plan for the Apache Kafka 3.0.0
> release.
>
> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466__;!!JhrIYaSK6lFZ!-k0g-tIlibi6VoGNY2-ZLKPCfAz2RJ2ICdx4IA4TfulZQIp7Gx7rhD9f0KyCN4Gh2VwyHw$
>
> New suggested dates for the release are as follows:
>
> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> Code Freeze is 14 July 2021 (new date, extended by two weeks)
>
> At least two weeks of stabilization will follow Code Freeze.
>
> The release plan is up to date and currently includes all the approved KIPs
> that are targeting 3.0.0.
>
> Please let me know if you have any objections with the recent extension of
> Feature Freeze and Code Freeze or any other concerns.
>
> Regards,
> Konstantine
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Ismael Juma]

Thanks Konstantine, +1 from me.

Ismael

On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
 wrote:

> Hi all,
>
> Please find below the updated release plan for the Apache Kafka 3.0.0
> release.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>
> New suggested dates for the release are as follows:
>
> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> Code Freeze is 14 July 2021 (new date, extended by two weeks)
>
> At least two weeks of stabilization will follow Code Freeze.
>
> The release plan is up to date and currently includes all the approved KIPs
> that are targeting 3.0.0.
>
> Please let me know if you have any objections with the recent extension of
> Feature Freeze and Code Freeze or any other concerns.
>
> Regards,
> Konstantine
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Konstantine Karantasis]

Thanks Sophie.

I'm also tracking the updates on the main KIP page and the Adopted KIPs
table periodically, moving newly adopted KIPs to the release plan.
But we'll definitely use the mailing list more as we approach KIP Freeze
and make sure we include everything that is ready by the time we hit
Feature Freeze.

Thanks for letting me know!
Konstantine


On Wed, May 26, 2021 at 3:04 PM Sophie Blee-Goldman
 wrote:

> Hey Konstantine, I did a quick skim over the Streams KIPs and found two
> more which had not
> been moved to the "Adopted" section on the main KIP page and are missing
> from the release
> notes. These are:
>
>- KIP-466: Add support for List serialization and deserialization
><
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-466%3A+Add+support+for+List%3CT%3E+serialization+and+deserialization
> >
>- KIP-725: Streamlining configurations for WindowedSerializer and
>WindowedDeserializer
><
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177047930
> >
>
>
> Thanks!
>  -Sophie
>
>
> On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
>  wrote:
>
> > Hi all,
> >
> > Please find below the updated release plan for the Apache Kafka 3.0.0
> > release.
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> >
> > New suggested dates for the release are as follows:
> >
> > KIP Freeze is 09 June 2021 (same date as in the initial plan)
> > Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> > Code Freeze is 14 July 2021 (new date, extended by two weeks)
> >
> > At least two weeks of stabilization will follow Code Freeze.
> >
> > The release plan is up to date and currently includes all the approved
> KIPs
> > that are targeting 3.0.0.
> >
> > Please let me know if you have any objections with the recent extension
> of
> > Feature Freeze and Code Freeze or any other concerns.
> >
> > Regards,
> > Konstantine
> >
>

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Sophie Blee-Goldman]

Hey Konstantine, I did a quick skim over the Streams KIPs and found two
more which had not
been moved to the "Adopted" section on the main KIP page and are missing
from the release
notes. These are:

   - KIP-466: Add support for List serialization and deserialization
   

   - KIP-725: Streamlining configurations for WindowedSerializer and
   WindowedDeserializer
   


Thanks!
 -Sophie


On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
 wrote:

> Hi all,
>
> Please find below the updated release plan for the Apache Kafka 3.0.0
> release.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>
> New suggested dates for the release are as follows:
>
> KIP Freeze is 09 June 2021 (same date as in the initial plan)
> Feature Freeze is 30 June 2021 (new date, extended by two weeks)
> Code Freeze is 14 July 2021 (new date, extended by two weeks)
>
> At least two weeks of stabilization will follow Code Freeze.
>
> The release plan is up to date and currently includes all the approved KIPs
> that are targeting 3.0.0.
>
> Please let me know if you have any objections with the recent extension of
> Feature Freeze and Code Freeze or any other concerns.
>
> Regards,
> Konstantine
>