In general I prefer to stick with the original time frame, but I believe
an additional month would be good for KIP-848.
Maybe we can cut down 2 weeks for the 4.1 and 4.2 releases each, to make
up for the time? Not a must; just an idea. We can also just accept a
one-time shift of the release time plan -- we did not really lose the
time effectively, as there was one additional release.
-Matthias
On 6/17/24 12:14 PM, David Jacot wrote:
+1 for the release plan. Thanks!
+1 for releasing 4.0 four months after 3.9. 4.0 is actually a pretty big
release as we will GA KIP-848, including new group coordinator and new
consumer rebalance protocol. This is a pretty big change :).
Best,
David
Le lun. 17 juin 2024 à 20:36, Colin McCabe <cmcc...@apache.org> a écrit :
Hi all,
Thanks, everyone.
Quick update: on the release plan page, I moved feature freeze forward and
code freeze by one week to make sure we can hit that. No other dates
changed.
With regard to 4.0, I was assuming that we'd do it 4 months after 3.9 was
released. I think for that release, we should front-load all the "remove
deprecated stuff" work that has piled up, and try to really hit all the
release milestone dates. I don't think 4.0 needs to be a very ambitious
release, it really is mostly about the removals and the new JDK (which are
a big deal, but I hope should fit within the normal timeframes). That being
said, if people want a shorter 4.0, I'm open to that, as long as we're
confident we could actually do that :)
best,
Colin
On Fri, Jun 14, 2024, at 20:56, Sophie Blee-Goldman wrote:
+1, thank you Colin
Given the July freeze deadlines, I take it we are going with the "short
3.9.0 release" option and that the existence of this release will impact
the 4.0.0 deadlines which will still follow the usual schedule -- in
other
words, this is an "additional release" outside of the regular timeline.
Is
this understanding correct?
On Fri, Jun 14, 2024 at 5:57 PM Chia-Ping Tsai <chia7...@gmail.com>
wrote:
+1 thanks Colin!
