That's my understanding, and I would advocate strongly to keep the 4.0
release schedule as planed originally.
The 3.9 one should really be an additional "out of schedule" release not
impacting any other releases.
-Matthias
On 6/14/24 1:29 PM, David Jacot wrote:
The plan sounds good to me. I suppose that we will follow our regular
cadence for 4.0 and release it four months after 3.9 (in November?). Is
this correct?
Best,
David
Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
<jsan...@confluent.io.invalid> a écrit :
+1 on the proposed release plan for 3.8.
Thanks!
On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma <m...@ismaeljuma.com> wrote:
+1 to the plan we converged on in this thread.
Ismael
On Fri, Jun 14, 2024 at 10:46 AM Josep Prat <josep.p...@aiven.io.invalid
wrote:
Hi all,
Thanks Colin, yes go ahead.
As we are now past code freeze I would like to ask everyone involved
in a
KIP that is not yet complete, to verify if what landed on the 3.8
branch
needs to be reverted or if it can stay. Additionally, I'll be pinging
KIPs
and Jira reporters asking for their status as some Jiras seem to have
all
related GitHub PRs merged but their status is still Open or In
Progress.
I'll be checking all the open blockers and check if they are really a
blocker or can be pushed.
Regarding timeline, I'll attempt to generate the first RC on Wednesday
or
Thursday, so please revert any changes you deem necessary by then. If
you
need more time, please ping me.
Best,
-----------------
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io | +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B
On Fri, Jun 14, 2024, 19:25 Colin McCabe <cmcc...@apache.org> wrote:
Hi all,
We have had many delays with releases this year. We should try to get
back
on schedule.
I agree with the idea that was proposed a few times in this thread of
drawing a line under 3.8 now, and doing a short 3.9 release. I
posted a
3.9
release plan here:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
I think we could start doing RCs for 3.8.0 as early as next week.
There
are a few things that need to be reverted first (anything related to
KIP-853 or KIP-966).
Josep, if you agree, I will update KIP-1012 to reflect that these
things
are landing in 3.9 rather than 3.8. And we can start doing all the
normal
release stuff. The main blocker JIRA I'm aware of is KAFKA-16946,
which
is
a very simple fix.
best,
Colin
On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
+1 on going with 3.8 release with the existing plan and targeting
the
required features in 3.9 timelines. 4.0 will be targeted in the
usual
cycle(4 months) after 3.9 is released.
On Fri, 14 Jun 2024 at 15:19, Edoardo Comar <edoardli...@gmail.com
wrote:
Josep,
past the deadline sorry but I can't see reasons not to cherry-pick
this
https://github.com/apache/kafka/pull/16326
On Wed, 12 Jun 2024 at 17:14, Josep Prat
<josep.p...@aiven.io.invalid
wrote:
Hi Edoardo,
Correct, you can still cherry-pick this one.
I'll send an email tomorrow morning (CEST) asking maintainers to
stop
cherry picking commits unless we discuss it beforehand.
Best,
On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <
edoardli...@gmail.com>
wrote:
Hi Josep, I understand I am still in time to cherry-pick on
3.8.0
https://github.com/apache/kafka/pull/16229
right?
thanks
On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko <i...@ivanyu.me>
wrote:
Hi,
I'll try to do all the fixes and changes for KIP-899 [1]
sooner
today,
but please proceed with the release if I don't manage.
Ivan
[1] https://github.com/apache/kafka/pull/13277
On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
Hi Luke,
I think Jose, also mentioned that it won't be ready for
v3.8.0
(but he
can
confirm this). My question now would be, given that it
seems
we
would
need
a v3.9.0, do you think it's important to include
https://github.com/apache/kafka/pull/16284 in v3.8.0?
Best,
On Wed, Jun 12, 2024 at 11:40 AM Luke Chen <
show...@gmail.com
wrote:
Hi Josep
For KIP-966, I think Calvin had mentioned he won't
complete
in
v3.8.0.
https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
For unclean leader election, all we need is this PR:
https://github.com/apache/kafka/pull/16284
For this PR, I think it needs one more week to be
completed.
Thanks.
Luke
On Wed, Jun 12, 2024 at 4:51 PM Josep Prat
<josep.p...@aiven.io.invalid>
wrote:
Hi all,
We are now really close to the planned code freeze
deadline
(today
EOD).
According to KIP-1012 [1] we agreed to stay in the 3.x
branch
until we
achieve feature parity regarding Zookeeper and KRaft.
The
two main
KIPs
identified that would achieve this are: KIP-853 [2]
and
KIP-966
[3].
At the moment of writing this email both KIPs are not
completed. My
question to the people driving both KIPs would be, how
much
more
time do
you think it's needed to bring these KIPs to
completion?
- If the time needed would be short, we could still
include
these
2 KIPs
in
the release.
- However, if the time needed would be on the scale of
weeks, we
should
continue with the release plan for 3.8 and after start
working on
the 3.9
release.
What are your thoughts?
[1]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
[2]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
[3]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
On Wed, Jun 12, 2024 at 10:40 AM Josep Prat <
josep.p...@aiven.io>
wrote:
Hi Rajini,
Yes, we could backport this one to the 3.8 branch.
Would
you be
able to
do
this once you merge this PR?
Thanks
On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
rajinisiva...@gmail.com
wrote:
Hi Josep,
The PR https://github.com/apache/kafka/pull/13277
for
KIP-899
looks
ready
to be merged (waiting for the PR build).The PR
changes
several
files,
but
is relatively straightforward and not risky. Also
the
changes
are
under
a
config that is not enabled by default. Since the
KIP
was
approved
before
KIP freeze, will it be ok to include in 3.8.0?
Thank you,
Rajini
On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
<josep.p...@aiven.io.invalid
wrote:
Hi all,
I just want to remind everybody that the code
freeze
deadline
is
approaching
<https://www.google.com/maps/search/%3E%3E+%3E+%3E+%3E+%3E+%3E+%3E+%3E%3E+%3E+approaching?entry=gmail&source=g>.
June 12th EOD is the deadline.
Please do not automatically backport any commit
to
the
3.8
branch
after
June 12th EOD. Ping me if you think the commit
should
be
backported
(fixes
failures in the branch or critical bug fixes).
Thanks all!
On Sat, Jun 1, 2024 at 8:43 PM José Armando
García
Sancio
<jsan...@confluent.io.invalid> wrote:
Hi Josep,
See my comments below.
On Wed, May 29, 2024 at 10:52 AM Josep Prat
<josep.p...@aiven.io.invalid
wrote:
So I would propose to leave the deadlines as
they
are and
manually
cherry
pick the commits related to KIP-853 and
KIP-966.
Your proposal sounds good to me. I suspect that
will
be
doing
feature
development for KIP-853 past the feature
freeze and
code
freeze
date.
Maybe feature development will be finished
around
the end
of June.
I'll make sure to cherry pick commits for
KIP-853
to
the 3.8
branch
once we have one.
Thanks,
--
-José
--
[image: Aiven] <https://www.aiven.io>
*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io | +491715557497
aiven.io <https://www.aiven.io> | <
https://www.facebook.com/aivencloud
<https://www.linkedin.com/company/aiven/> <
https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu
Valtonen
Amtsgericht Charlottenburg, HRB 209739 B
--
[image: Aiven] <https://www.aiven.io>
*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io | +491715557497
aiven.io <https://www.aiven.io> |
<https://www.facebook.com/aivencloud>
<https://www.linkedin.com/company/aiven/> <
https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B
--
[image: Aiven] <https://www.aiven.io>
*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io | +491715557497
aiven.io <https://www.aiven.io> | <
https://www.facebook.com/aivencloud
<https://www.linkedin.com/company/aiven/> <
https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B
--
[image: Aiven] <https://www.aiven.io>
*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io | +491715557497
aiven.io <https://www.aiven.io> | <
https://www.facebook.com/aivencloud>
<https://www.linkedin.com/company/aiven/> <
https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B
--
[image: Aiven] <https://www.aiven.io>
*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io | +491715557497
aiven.io <https://www.aiven.io> | <
https://www.facebook.com/aivencloud>
<https://www.linkedin.com/company/aiven/> <
https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B
--
-José
