Thanks for the heads up Konstantine: I am currently working on these issues below and should send new PRs by the end of the week.
My changes should be merged into the 3.0 branch as well as trunk. I have marked them as "blockers" for tracking purposes and for the PR merges. *Add Missing Class-Level Javadoc to Descendants of org.apache.kafka.common.errors.ApiException* https://issues.apache.org/jira/browse/KAFKA-12644 *Migrate all Tests to New API and Remove Suppression for Deprecation Warnings related to KIP-633* https://issues.apache.org/jira/browse/KAFKA-12994 *Improve Javadocs for API Changes from KIP-633* https://issues.apache.org/jira/browse/KAFKA-13021 They are all improvements and the release can proceed without it but I wanted to make the workflow smoother. Please let me know if you have any questions or concerns. Thanks. On Tue, Jul 6, 2021 at 3:38 PM Konstantine Karantasis < kkaranta...@apache.org> wrote: > Hi Kafka developers and friends, > > The release branch for Apache Kafka 3.0 (with version 3.0.0) has been > created > (https://github.com/apache/kafka/tree/3.0). > > The trunk branch is about to be bumped to 3.1.0-SNAPSHOT via > https://github.com/apache/kafka/pull/10981 > > At this point, I'll be reviewing the open JIRA tickets to move every > non-blocker from this release to the next one. > > Going forward, most changes should land only on the trunk branch. > > Blockers (existing and new that we discover while testing the release) will > be double-committed. > Please discuss with your reviewers whether your PR should go to trunk or to > trunk as well as 3.0 so they can merge accordingly. > > The 3.0 branch going live is an excellent opportunity to focus on testing > the features you aim to include in the upcoming release and making sure > that tests are stable, dependable and offer good coverage. > > Please help us test the release and make sure it gets out the door stable > and with high quality. > > Sincerely, > Konstantine >
