Hi Stanislav, +1 to what Luke mentioned in the earlier email. I have also replied to your comment on https://issues.apache.org/jira/browse/KAFKA-15147
These are minor changes and we plan to target the remaining changes to be merged in the next few days(before 20th Dec). Thanks, Satish. On Thu, 14 Dec 2023 at 17:54, Luke Chen <show...@gmail.com> wrote: > Hi Stanislav, > > For KIP-963, there are only 1 remaining task and 2 PRs which should be > close to get merged. (ref: > https://issues.apache.org/jira/browse/KAFKA-15147) > Since this is an improvement for tiered storage metrics, not a huge > change, I'd like to backport them into 3.7 branch if no objection from > you. > > Thanks. > Luke > > On Thu, Dec 14, 2023 at 5:15 PM Stanislav Kozlovski > <stanis...@confluent.io.invalid> wrote: > > > > Hey all, > > > > (thanks to Josep for reviewing the 3.8 bump PR) > > > > I have two more PRs to get reviewed regarding the release: > > - targeting trunk: MINOR: Update documentation.html with the 3.7 release > > #15010 <https://github.com/apache/kafka/pull/15010> > > - targeting 3.7: MINOR: Update documentation.html with the 3.7 release > > #15011 <https://github.com/apache/kafka/pull/15011> > > > > Additionally, I have one ask: > > - if you are reading this message, can you double-check the list of KIPs > > being released in the Release Page > > <https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.7.0> > and > > if you recognize any KIP you are involved it - can you ensure that the > data > > in the page & the associated JIRA/KIP (target release, merge status, vote > > status) is up to date? > > > > I have myself went over the list of KIPs and a bit of the commit > history. I > > think KIPs: > > - KIP-998: Give ProducerConfig(props, doLog) constructor protected access > > - KIP-938: Add more metrics for measuring KRaft performance > > are slipping this release. > > > > By far our biggest feature this release, KIP-848 The Next Generation of > the > > Consumer Rebalance Protocol, is a bit on the border. The main PR that KIP > > is dependent on is this KAFKA-15456: Commit/Fetch error handling > > improvements and V9 support #14557 > > <https://github.com/apache/kafka/pull/14557>. > > While it's a gray area, I am weighing this change more on the > stabilization > > side as well as allowing it to come in the middle of feature freeze for > two > > chief reasons: a) it fixes issues that were recently discovered, hence > can > > be marked as stabilization work and b) it only touches the code path used > > for Early Access, and not the existing production code path (hence > doesn't > > substantially risk the release) > > > > Additionally, KIP-858 has one minor but important change pending > > <https://github.com/apache/kafka/pull/14984>. > > > > With that, I remind you that there are only 6 days to code freeze! It's > not > > long until we will have our very first Apache Kafka 3.7 RC! Let's get > this > > shipped. > > > > Best, > > Stanislav > > > > On Tue, Dec 12, 2023 at 2:56 PM Stanislav Kozlovski < > stanis...@confluent.io> > > wrote: > > > > > Hello Kafka developers and friends, > > > > > > As promised, we now have a release branch for 3.7 release. > > > Trunk is being bumped to 3.8.0-SNAPSHOT (please help review the PR < > https://github.com/apache/kafka/pull/14993>). > > > > > > I'll be going over the JIRAs to move every non-blocker from this > release to the next release. > > > > > > From this point, most changes should go to trunk. > > > *- Blockers (existing and new that we discover while testing the > release) will be double-committed.* > > > *- Please discuss with your reviewer whether your PR should go to > trunk or to trunk+release so they can merge accordingly.* > > > *- Please help us test the release!* > > > > > > Thanks! > > > > > > -- > > > Best, > > > Stanislav > > > > > > > > > -- > > Best, > > Stanislav >
