Hi Konstantine,

Please Add the following KIPs into Kafka 3.0 plan. In the case of KIP-653,
it was passed already but not included in the 2.8.0 release.

- KIP-653: Upgrade log4j to log4j2
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-653%3A+Upgrade+log4j+to+log4j2>
- KIP-719: Add Log4J2 Appender
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-719%3A+Add+Log4J2+Appender>

I also updated the proposal documents reflecting the recent changes to our
codebase. Especially:

1. KIP-653 document
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-653%3A+Upgrade+log4j+to+log4j2>
now explains which modules will be migrated and why.
2. KIP-719 document
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-719%3A+Add+Log4J2+Appender>
now explains not only the log4j2-appender plan but also upgrading the
omitted modules in KIP-653 into log4j2.

As you can see here, those two KIPs are the different parts of the same
problem. I believe the community will have a good grasp on why both KIPs
are best if released altogether.

Best,
Dongjin

On Fri, May 14, 2021 at 8:51 AM Konstantine Karantasis
<konstant...@confluent.io.invalid> wrote:

> Hi all,
>
> Lots of good progress recently towards the 3.0.0 release and given that we
> are now a little less than a month away from the first milestone, I wanted
> to post a status update and a reminder of the upcoming dates for this major
> release.
>
> According to the current release plan for Apache Kafka 3.0.0:
>
> KIP Freeze is 09 Jun 2021
>
> Feature Freeze is 16 Jun 2021
>
> Code Freeze is 30 Jun 2021
>
> and at least two weeks of stabilization will follow Code Freeze.
>
> Since the initial announcement, the list of adopted KIPs targeting 3.0.0
> has grown with 10 additional KIPs. Several more are under discussion and
> voting.
>
> New KIPs will be accepted up until the KIP Freeze and of course the actual
> set of features that will make it to 3.0.0 will be finalized right after
> Feature Freeze.
>
> With that in mind, if you want to assist the 3.0.0 release process, please
> make sure that the adopted KIPs which you aim to include in this major
> release have the right number in the “Release” column of the table in the
> KIP wiki and that their respective Jira tickets include 3.0.0 in the "Fix
> Version/s" label.
>
> Kafka Improvement Proposals:
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
>
> Release Plan 3.0.0:
>
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.0.0
>
> Regards,
>
> Konstantine
>
>
> On Wed, Mar 10, 2021 at 10:28 AM Konstantine Karantasis <
> konstant...@confluent.io> wrote:
>
> >
> > Thank you and hi again.
> >
> > I just published a release plan at:
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
> >
> > I have included all the currently approved KIPs. I'm expecting this list
> > to grow as we approach KIP freeze.
> >
> > The KIP freeze date for Apache Kafka 3.0 is June 9th, 2021.
> >
> > Please let me know if you have any objections.
> >
> > Regards,
> > Konstantine
> >
> >
> > On Wed, Feb 24, 2021 at 9:45 AM Chia-Ping Tsai <chia7...@apache.org>
> > wrote:
> >
> >> Thanks for taking over this hard job! +1
> >>
> >> On 2021/02/23 08:02:09, Konstantine Karantasis <
> konstant...@confluent.io>
> >> wrote:
> >> > Hi all,
> >> >
> >> > Given that we seem to reach an agreement that the feature release
> after
> >> the
> >> > upcoming 2.8.0 will be 3.0.0, I'd like to volunteer to be the release
> >> > manager for the Apache Kafka 3.0.0 release.
> >> >
> >> > It's a major release, so I thought it'd be helpful to start planning a
> >> bit
> >> > in advance.
> >> >
> >> > If there are no objections, I'll start working on a release plan in
> the
> >> > next few days.
> >> >
> >> > Best,
> >> > Konstantine
> >> >
> >>
> >
>


-- 
*Dongjin Lee*

*A hitchhiker in the mathematical world.*



*github:  <http://goog_969573159/>github.com/dongjinleekr
<https://github.com/dongjinleekr>keybase: https://keybase.io/dongjinleekr
<https://keybase.io/dongjinleekr>linkedin: kr.linkedin.com/in/dongjinleekr
<https://kr.linkedin.com/in/dongjinleekr>speakerdeck: speakerdeck.com/dongjin
<https://speakerdeck.com/dongjin>*

Reply via email to