Added the jira query link for the blocker tickets that needed to help. https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20fixVersion%20%3D%203.2.0%20AND%20priority%20%3D%20Blocker%20AND%20assignee%20in%20(EMPTY)%20AND%20%20status%20not%20in%20(resolved%2C%20closed)%20ORDER%20BY%20priority%20DESC%2C%20status%20DESC%2C%20updated%20DESC
Thank you. Luke On Thu, Mar 24, 2022 at 9:04 PM Bruno Cadonna <cado...@apache.org> wrote: > Hi Kafkateers, > > we still have 16 blocker tickets and 7 critical tickets that are not > resolved for AK 3.2. > > Out of these tickets 13 are flaky tests. Those flaky tests were disabled > to not hinder further development > (https://github.com/apache/kafka/pull/11895). Still we need to > investigate whether those flaky tests are: > - flaky (then we need to fix the test) > - surfacing an actual bug (then we need to fix the production code) > - not of great value (then we should remove the test to avoid noise) > > So please help investigating those flaky tests and resolve them by > fixing the test, fixing production code, or removing the test. > > Besides the flaky tests, also the other blocker tickets and critical > tickets need some attention. > > Best, > Bruno > > On 21.03.22 22:22, Bruno Cadonna wrote: > > Hi Kafkateers, > > > > Last week we reached feature freeze for the next major release of Apache > > Kafka. > > > > I cut the release branch for 3.2 and bumped trunk to 3.3.0-SNAPSHOT. > > From this point, commits that should go into 3.2.0 should be merged > > into trunk and cherry-picked to 3.2. > > > > > > I removed the KIPs for which I think the main PRs were not merged from > > the release plan for AK 3.2.0. Please, verify the plan and let me know > > if I removed a KIP that should not have been removed. > > > > Until code freeze on 30 March, please help with fixing flaky tests, > > finding bugs, testing, and updating documentation. > > > > You can find the list of open issues for 3.2.0 under the following link: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20fixVersion%20%3D%203.2.0%20AND%20status%20not%20in%20(resolved%2C%20closed)%20ORDER%20BY%20priority%20DESC%2C%20status%20DESC%2C%20updated%20DESC%20%20%20%20%20%20%20%20%20 > > > > > > > > Best, > > Bruno > > > > On 15.03.22 15:11, Bruno Cadonna wrote: > >> Hi all, > >> > >> A quick reminder that feature freeze for Apache 3.2.0 is tomorrow. > >> Please make sure to get your features merged into trunk. > >> > >> I will cut the release branch on Monday. > >> > >> Best, > >> Bruno > >> > >> On 07.03.22 15:03, Bruno Cadonna wrote: > >>> Hi Kafkateers, > >>> > >>> Last week we reached KIP freeze for the next major release 3.2.0 of > >>> Apache Kafka. > >>> > >>> I have updated the release plan for AK 3.2.0 with all the KIPs that > >>> passed the vote last week. > >>> > >>> Please, verify the plan and let me know if any KIP should be added > >>> to or removed from the release plan. > >>> > >>> For the KIPs which are still in progress, please work closely with your > >>> reviewers to make sure that they land on time for the feature freeze. > >>> > >>> The next milestone for the AK 3.2.0 release is feature freeze on > >>> March 16th 2022. > >>> > >>> Best, > >>> Bruno > >>> > >>> On 01.03.22 17:41, Bruno Cadonna wrote: > >>>> Hi all, > >>>> > >>>> A quick reminder that KIP freeze for the Apache 3.2.0 is tomorrow. > >>>> Please make sure to close your votes if you want to add a KIP to the > >>>> release plan. > >>>> > >>>> Best, > >>>> Bruno > >>>> > >>>> On 15.02.22 12:37, Bruno Cadonna wrote: > >>>>> Hi all, > >>>>> > >>>>> I published a release plan for the Apache Kafka 3.2.0 release here: > >>>>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.2.0 > >>>>> > >>>>> KIP Freeze: 2 March 2022 > >>>>> Feature Freeze: 16 March 2022 > >>>>> Code Freeze: 30 March 2022 > >>>>> > >>>>> At least two weeks of stabilization will follow Code Freeze. > >>>>> > >>>>> Please let me know if should add or remove KIPs from the plan or if > >>>>> you have any other objections. > >>>>> > >>>>> Best, > >>>>> Bruno > >>>>> > >>>>> > >>>>> On 04.02.22 16:03, Bruno Cadonna wrote: > >>>>>> Hi, > >>>>>> > >>>>>> I'd like to volunteer to be the release manager for our next > >>>>>> feature release, 3.2.0. If there are no objections, I'll send > >>>>>> out the release plan soon. > >>>>>> > >>>>>> Best, > >>>>>> Bruno >
