Hey everyone,

Thanks for all the contribution! Just a kind reminder that the code is now
frozen for 2.1.0 release.

Thanks,
Dong

On Mon, Oct 1, 2018 at 4:31 PM Dong Lin <lindon...@gmail.com> wrote:

> Hey everyone,
>
> Hope things are going well!
>
> Just a kind reminder that the feature freeze time is end of day today.
> Major features (e.g. KIP implementation) need to be merged and minor
> features need to be have PR ready. After today I will move pending JIRAs to
> the next release as appropriate.
>
> Cheers,
> Dong
>
>
>
> On Wed, 26 Sep 2018 at 1:06 AM Dong Lin <lindon...@gmail.com> wrote:
>
>> Hey Edoardo,
>>
>> Certainly, let's add it to this release since it has passed vote. KIP-81
>> was previously marked as WIP for 2.0.0 release. I updated to be WIP for
>> 2.1.0 release in
>> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
>>  and
>> added it to
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554044
>> .
>>
>> Thanks,
>> Dong
>>
>> On Tue, Sep 25, 2018 at 1:52 AM Edoardo Comar <eco...@uk.ibm.com> wrote:
>>
>>> Hi Dong
>>> many thanks for driving the release!
>>>
>>> KIP-81 previously voted as adopted has a ready-to-review JIRA and PR.
>>> Shall we just amend the wiki ?
>>> --------------------------------------------------
>>> Edoardo Comar
>>> IBM Event Streams
>>> IBM UK Ltd, Hursley Park, SO21 2JN
>>>
>>>
>>>
>>>
>>> From:        Dong Lin <lindon...@gmail.com>
>>> To:        dev <dev@kafka.apache.org>, Users <us...@kafka.apache.org>,
>>> kafka-clients <kafka-clie...@googlegroups.com>
>>> Date:        25/09/2018 08:17
>>> Subject:        Re: [DISCUSS] Apache Kafka 2.1.0 Release Plan
>>> ------------------------------
>>>
>>>
>>>
>>> Hey everyone,
>>>
>>> According to the previously discussed schedule, I have updated
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554044
>>> to include all the KIPs that have passed vote at this moment to be
>>> included
>>> in Apache Kafka 2.1.0 release. Other KIPs that have not passed vote will
>>> need to be included in the next feature release.
>>>
>>> Just a reminder that the feature freeze data is Oct 1, 2018. In order to
>>> be
>>> included in the release, major features need to be merged and minor
>>> features need to be have PR ready. Any feature not in this state will be
>>> automatically moved to the next release after Oct 1.
>>>
>>> Regards,
>>> Dong
>>>
>>> On Tue, Sep 25, 2018 at 12:02 AM Dong Lin <lindon...@gmail.com> wrote:
>>>
>>> > cc us...@kafka.apache.org and kafka-clie...@googlegroups.com
>>> >
>>> > On Sun, Sep 9, 2018 at 5:31 PM Dong Lin <lindon...@gmail.com> wrote:
>>> >
>>> >> Hi all,
>>> >>
>>> >> I would like to be the release manager for our next time-based feature
>>> >> release 2.1.0.
>>> >>
>>> >> The recent Kafka release history can be found at
>>> >> https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan
>>> .
>>> >> The release plan (with open issues and planned KIPs) for 2.1.0 can be
>>> found
>>> >> at
>>> >>
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554044
>>> >> .
>>> >>
>>> >> Here are the dates we have planned for Apache Kafka 2.1.0 release:
>>> >>
>>> >> 1) KIP Freeze: Sep 24, 2018.
>>> >> A KIP must be accepted by this date in order to be considered for this
>>> >> release)
>>> >>
>>> >> 2) Feature Freeze: Oct 1, 2018
>>> >> Major features merged & working on stabilization, minor features have
>>> PR,
>>> >> release branch cut; anything not in this state will be automatically
>>> moved
>>> >> to the next release in JIRA.
>>> >>
>>> >> 3) Code Freeze: Oct 15, 2018 (Tentatively)
>>> >>
>>> >> The KIP and feature freeze date is about 3-4 weeks from now. Please
>>> plan
>>> >> accordingly for the features you want push into Apache Kafka 2.1.0
>>> release.
>>> >>
>>> >>
>>> >> Cheers,
>>> >> Dong
>>> >>
>>> >
>>>
>>>
>>>
>>> Unless stated otherwise above:
>>> IBM United Kingdom Limited - Registered in England and Wales with number
>>> 741598.
>>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
>>> 3AU
>>>
>>

Reply via email to