Hi Stanislav, Thanks for putting this together! I think the "Ensure that release candidates include artifacts for the new Connect test-plugins module" section (which I'm guessing was copied over from the 3.6.0 release plan?) can be removed; we made sure that those artifacts were present for 3.6.0, and I don't anticipate any changes that would make them likelier to be accidentally dropped in subsequent releases than any other Maven artifacts that we publish.
Also, can we add KIP-976 ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-976%3A+Cluster-wide+dynamic+log+adjustment+for+Kafka+Connect) to the release plan? The vote thread for it passed last week and I've published a complete PR (https://github.com/apache/kafka/pull/14538), so it shouldn't be too difficult to get things merged in time for 3.7.0. Cheers, Chris On Sat, Oct 14, 2023 at 3:26 PM Stanislav Kozlovski <stanis...@confluent.io.invalid> wrote: > Thanks for letting me drive it, folks. > > I've created the 3.7.0 release page here: > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.7.0 > It outlines the key milestones and important dates for the release. > > In particular, since the last two releases slipped their originally > targeted release date by taking an average of 46 days after code freeze (as > opposed to the minimum which is 14 days), I pulled the dates forward to try > and catch up with the original release schedule. > You can refer to the last release during the Christmas holiday season - > Apache > Kafka 3.4 > <https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.4.0> - > to > see sample dates. > > The currently proposed dates are: > > *KIP Freeze - 18th November *(Saturday) > *This is 1 month and four days from now - rather short - but I'm afraid is > the only lever that's easy to pull forward.* > As usual, a KIP must be accepted by this date in order to be considered for > this release. Note, any KIP that may not be implemented in a week, or that > might destabilize the release, should be deferred. > > *Feature Freeze - 8th December* (Friday) > *This follows 3 weeks after the KIP Freeze, as has been the case in our > latest releases.* > By this point, we want all major features to be merged & us to be working > on stabilisation. Minor features should have PRs, the release branch should > be cut; anything not in this state will be automatically moved to the next > release in JIRA > > *Code Freeze - 20th December* (Wednesday) > > *Critically, this is before the holiday season and ends in the middle of > the week, to give contributors more time and flexibility to address any > last-minute without eating into the time people usually take holidays. It > comes 12 days after the Feature Freeze.This is two days shorter than the > usual code freeze window. I don't have a strong opinion and am open to > extend it to Friday, or trade off a day/two with the KF<->FF date range.* > > *Release -* *after January 3rd*. > *It comes after a minimum of two weeks of stabilization, so the earliest we > can start releasing is January 3rd. We will move as fast as we can and aim > completing it as early in January as possible.* > > As for the initially-populated KIPs in the release plan, I did the > following: > > I kept 4 KIPs that were mentioned in 3.6, saying they would have minor > parts finished in 3.7 (as the major ones went out in 3.6) > - KIP-405 Tiered Storage mentioned a major part went out with 3.6 and the > remainder will come with 3.7 > - KIP-890 mentioned Part 1 shipped in 3.6. I am assuming the remainder will > come in 3.7, and have contacted the author to confirm. > - KIP-926 was partially implemented in 3.6. I am assuming the remainder > will come in 3.7, and have contacted the author to confirm. > - KIP-938 mentioned that the majority was completed and a small remainder > re: ForwardingManager metrics will come in 3.7. I have contacted the author > to confirm. > > I then went through the JIRA filter which looks at open issues with a Fix > Version of 3.7 and added KIP-770, KIP-858, and KIP-980. > I also found a fair amount of JIRAs that were targeting the 3.7 release but > consecutively had no activity on them for the past few releases. For most > of those, I pinged the author and explicitly asked if it's going to aim to > make it to 3.7. I have not included those here and will not until I hear > confirmation. > > Please review the plan and provide any additional information or updates > regarding KIPs that target this release version (3.7). > If you have authored any KIPs that have an inaccurate status in the list, > or are not in the list and should be, or are in the list and should not be > - please inform me in this thread so that I can keep the document accurate > and up to date. > > Excited to get this release going! > > All the best, > Stanislav > > On Tue, Oct 10, 2023 at 9:12 AM Bruno Cadonna <cado...@apache.org> wrote: > > > Thanks Stan! > > > > +1 > > > > Best, > > Bruno > > > > On 10/10/23 7:24 AM, Luke Chen wrote: > > > Thanks Stanislav! > > > > > > On Tue, Oct 10, 2023 at 3:05 AM Josep Prat <josep.p...@aiven.io.invalid > > > > > wrote: > > > > > >> Thanks Stanislav! > > >> > > >> ——— > > >> Josep Prat > > >> > > >> Aiven Deutschland GmbH > > >> > > >> Alexanderufer 3-7, 10117 Berlin > > >> > > >> Amtsgericht Charlottenburg, HRB 209739 B > > >> > > >> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > >> > > >> m: +491715557497 > > >> > > >> w: aiven.io > > >> > > >> e: josep.p...@aiven.io > > >> > > >> On Mon, Oct 9, 2023, 20:05 Chris Egerton <fearthecel...@gmail.com> > > wrote: > > >> > > >>> +1, thanks Stanislav! > > >>> > > >>> On Mon, Oct 9, 2023, 14:02 Bill Bejeck <bbej...@gmail.com> wrote: > > >>> > > >>>> +1 > > >>>> > > >>>> Thanks, Stanislav! > > >>>> > > >>>> -Bill > > >>>> > > >>>> On Mon, Oct 9, 2023 at 1:59 PM Ismael Juma <m...@ismaeljuma.com> > wrote: > > >>>> > > >>>>> Thanks for volunteering Stanislav! > > >>>>> > > >>>>> Ismael > > >>>>> > > >>>>> On Mon, Oct 9, 2023 at 10:51 AM Stanislav Kozlovski > > >>>>> <stanis...@confluent.io.invalid> wrote: > > >>>>> > > >>>>>> Hey all! > > >>>>>> > > >>>>>> I would like to volunteer to be the release manager driving the > > >> next > > >>>>>> release - Apache Kafka *3.7.0*. > > >>>>>> > > >>>>>> If there are no objections, I will start and share a release plan > > >>> soon > > >>>>>> enough! > > >>>>>> > > >>>>>> Cheers, > > >>>>>> Stanislav > > >>>>>> > > >>>>> > > >>>> > > >>> > > >> > > > > > > > > -- > Best, > Stanislav >
