Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
MIME-Version: 1.0
In-Reply-To: <CAE1jLMPT=eQxCJ-XCAaZOmP91GNkvq_KaXHpRtXWL-u=ezwTBg@mail.gmail.com>
References: <CAE1jLMPUO5PsB+nfeXkKx3V3FL4_Ka-Vo5zt+OZXY-cHOs80Wg@mail.gmail.com>
 <CAD5tkZZ=nJKw4Uv4bL+1KEhrKw8C_GEjDpcU_tAea3ahCJtB7Q@mail.gmail.com>
 <CAFXAVc5=DRGGaSHF0tiUKpmBQUCD3JLfKC2tubMQoo2xScV=kg@mail.gmail.com>
 <CAD5tkZZhvVfJ9ucyzEoSXfeRVaRoi2g11g+fqUbYXf2nQi+6Bg@mail.gmail.com>
 <CAFXAVc4k_TVs5B75FDPF7FRDq5Q-3TP0aEaqzzGg38mYoHpN=w@mail.gmail.com>
 <CAD5tkZb-=BoV0cfApuvJhC-bbAQXdVx0WwUV3P_YRPa+85P-hw@mail.gmail.com>
 <CAE1jLMMFSeRMa3xFuppx0Lmzb0epEg3xmuLwsbw=YASbjMeOog@mail.gmail.com>
 <CAD5tkZYcFQwu-6BESkxf=SSCgHB1iaZ_PR0Vu7_Y3CeGZM03wA@mail.gmail.com>
 <CAE1jLMMHr4CaypMmuJuAQRzDjApPSucsSMN+=YLUyeKoakfmGg@mail.gmail.com> <CAE1jLMPT=eQxCJ-XCAaZOmP91GNkvq_KaXHpRtXWL-u=ezwTBg@mail.gmail.com>
From: Ewen Cheslack-Postava <ewen@confluent.io>
Date: Mon, 16 Jan 2017 11:47:15 -0800
Message-ID: <CAE1jLMPhtM33VV8mQoff0zYT=gipsR3kvYNPNUQO7_xqKyb14A@mail.gmail.com>
Subject: Re: 0.10.2.0 release planning
To: dev@kafka.apache.org
Content-Type: multipart/alternative; boundary=001a1145247e5f269505463b7364
archived-at: Mon, 16 Jan 2017 19:47:26 -0000

--001a1145247e5f269505463b7364
Content-Type: text/plain; charset=UTF-8

Thanks to everyone that helped with development and review of the KIPs. We
got nearly everything we aimed for in! We'll give the release a couple of
more weeks to fully bake and stabilize, focusing mostly on getting bug
fixes and improved tests into the release branch.

I've cut the 0.10.2 release branch and trunk is now marked as
0.10.3.0-SNAPSHOT. Committers will now need to double commit anything they
want to see in the 0.10.2.0 release. Contributors can help with this by
making sure they make a note in PRs for anything that needs double
committing.

I'm also working on culling the bugs marked 0.10.2.0 since we still have a
very large number of them left. Of course all PRs are helpful, but I've
noticed quite a few marked "Critical" that have been bumped from multiple
releases. If you're looking at getting bug fixes in for this release,
prioritizing by the marked importance level would be greatly appreciated.

Next release milestone will be code freeze on Jan 27th, at which point
we'll start releasing and testing RCs.

-Ewen

On Mon, Jan 9, 2017 at 10:20 PM, Ewen Cheslack-Postava <ewen@confluent.io>
wrote:

> As a quick follow up, for community members looking for areas they are
> familiar with to review I have updated the KIP table at the bottom of
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.2.0
> with a column annotating the area of code the KIP/PR is related to (e.g.
> consumer, streams, connect, broker) to help you find which PRs you are
> comfortable reviewing quickly.
>
> -Ewen
>
> On Mon, Jan 9, 2017 at 5:16 PM, Ewen Cheslack-Postava <ewen@confluent.io>
> wrote:
>
>> Hey folks,
>>
>> Here's a quick update and reminder that feature freeze is coming up on
>> Friday (don't worry, you'll have through the end of the day to merge stuff).
>>
>> Most importantly, *everyone* can contribute to landing the many KIPs and
>> features we're trying to get in by Friday. Committers need to take a final
>> pass to get PRs in, but it really helps throughput if additional reviewers
>> have taken a pass as well. And some PRs are tricky & large, and could use
>> more eyes if possible.
>>
>> * Reminder that you can find the release plan here:
>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.2.0
>> * We've had a ton of KIPs get voted through. I've moved everything that
>> is passed and everything that already has enough votes (and is planned for
>> 0.10.2.0 instead of later) onto the planning wiki. The total count is at
>> 20! We may even have 1 more that I'm aware of that could make it.
>> * There are 14 PRs still outstanding for KIPs (even a few to be filed
>> still).
>> * I've made sure we have "reviewers" assigned for all the JIRAs. These
>> are by no means final and may shift. In particular, Guozhang and Jason are
>> currently on the hook for quite a few -- if any committers not currently
>> represented on the list have throughput, please feel free to grab
>> ownership. Also, please note that we want a committer associated with each
>> not to be required to do all review, but so we have someone to ping to get
>> the final version committed.
>> * That's a lot of work by Friday and the idea of time based releases is
>> to get a regular release cadence even if not everything we want in a
>> release manages to make it. Please try to be responsive to feedback to
>> increase the likelihood that reviewers can get back to your PR and commit
>> it; also don't stress if your KIP doesn't make it in -- as soon as we
>> generate branches we can get your PR committed to trunk and ready for the
>> subsequent release.
>>
>> As I said above, more eyes on PRs will help. If we can step up the
>> community reviews this week, we're likely to land more features so we have
>> time to stabilize before release.
>>
>> If you have any questions re: the release, please ask. Otherwise I'll
>> send another update later in the week.
>>
>> Thanks all,
>> -Ewen
>>
>> On Thu, Jan 5, 2017 at 2:03 AM, Ismael Juma <ismael@juma.me.uk> wrote:
>>
>>> Good clarification. A couple more things:
>>>
>>> 1. KIP-90 (which is currently scheduled for 0.10.2.0) uses create/delete
>>> topics in the context of Streams. So, there is a user-visible impact.
>>> 2. KIP-4 ACL hasn't been voted yet so that would have to happen too
>>> before
>>> it could be included.
>>>
>>> Ismael
>>>
>>> On Thu, Jan 5, 2017 at 5:11 AM, Ewen Cheslack-Postava <ewen@confluent.io
>>> >
>>> wrote:
>>>
>>> > Just to clarify this a bit, the additions made so far add the
>>> server-side
>>> > handling of the new protocols. But it does not include any user-facing
>>> API
>>> > changes to enable use of these features. Because of this, it's not
>>> > particularly useful to users and not really worth mentioning. It'd
>>> mostly
>>> > be useful to non-Java client developers that want to add support for
>>> this
>>> > functionality to their libraries. We can try to advertise it to them a
>>> bit,
>>> > but the ones that actively maintain and regularly add improvements like
>>> > this are generally already watching the KIPs and at least monitor
>>> > kafka-dev.
>>> >
>>> > (Note that there's also a longstanding WIP patch for list/alter ACLs
>>> > https://github.com/apache/kafka/pull/1005. Grant's been inactive for a
>>> > bit,
>>> > but if he comes back to that patch, it'd be possible to squeeze it into
>>> > 0.10.2.0)
>>> >
>>> > -Ewen
>>> >
>>> > On Wed, Jan 4, 2017 at 8:29 AM, Ismael Juma <ismael@juma.me.uk> wrote:
>>> >
>>> > > 0.10.1.0 was the release with partial KIP-4 functionality: we added
>>> > create
>>> > > topics and delete topics to the Kafka protocol. 0.10.2.0 doesn't
>>> improve
>>> > > things so far.
>>> > >
>>> > > Ismael
>>> > >
>>> > > On Wed, Jan 4, 2017 at 4:28 PM, Tom Crayford <tcrayford@heroku.com>
>>> > wrote:
>>> > >
>>> > > > Ismael,
>>> > > >
>>> > > > Thanks. Does this mean there's partially implemented KIP-4
>>> > functionality
>>> > > > landing in 0.10.2.0? It seems like having release notes for that
>>> > > > functionality would be quite important.
>>> > > >
>>> > > > On Wed, Jan 4, 2017 at 4:16 PM, Ismael Juma <ismael@juma.me.uk>
>>> wrote:
>>> > > >
>>> > > > > Hi Tom,
>>> > > > >
>>> > > > > Thanks for the heads-up. Most of KIP-35 was included in
>>> 0.10.0.0. The
>>> > > > > remaining PR was merged to trunk (will be in 0.10.2.0), so I
>>> closed
>>> > the
>>> > > > > JIRA (and changed KAFKA-3308 to be a standalone task as it wasn't
>>> > part
>>> > > of
>>> > > > > KIP-35).
>>> > > > >
>>> > > > > About KIP-4, that's a big KIP and it will continue to be open
>>> after
>>> > > > > 0.10.2.0 is released. We haven't made much progress on that front
>>> > > during
>>> > > > > this release cycle, but I hope we'll do better for the next
>>> release
>>> > > > cycle.
>>> > > > >
>>> > > > > Ismael
>>> > > > >
>>> > > > > On Wed, Jan 4, 2017 at 4:08 PM, Tom Crayford <
>>> tcrayford@heroku.com>
>>> > > > wrote:
>>> > > > >
>>> > > > > > Thanks for running the release and being so transparent around
>>> > plans,
>>> > > > > it's
>>> > > > > > a great boon to the community.
>>> > > > > >
>>> > > > > > Looking at the plan (
>>> > > > > > https://cwiki.apache.org/confluence/display/KAFKA/
>>> > > > Release+Plan+0.10.2.0
>>> > > > > ),
>>> > > > > > I
>>> > > > > > see KIP-4 and KIP-35 under "Open Issues", but not under
>>> "Planned
>>> > KIP
>>> > > > > > Content". Are those KIPs landing in this release or not?
>>> > > > > >
>>> > > > > > Thanks
>>> > > > > >
>>> > > > > > Tom
>>> > > > > >
>>> > > > > > On Mon, Jan 2, 2017 at 10:27 PM, Ismael Juma <
>>> ismael@juma.me.uk>
>>> > > > wrote:
>>> > > > > >
>>> > > > > > > Thanks for the update and for managing the next release
>>> Ewen. :)
>>> > > > > > >
>>> > > > > > > Ismael
>>> > > > > > >
>>> > > > > > > On Mon, Jan 2, 2017 at 10:22 PM, Ewen Cheslack-Postava <
>>> > > > > > ewen@confluent.io>
>>> > > > > > > wrote:
>>> > > > > > >
>>> > > > > > > > Hey folks,
>>> > > > > > > >
>>> > > > > > > > We're quickly approaching our next time-based release. If
>>> you
>>> > > > missed
>>> > > > > > any
>>> > > > > > > of
>>> > > > > > > > the updates on the new time-based releases we'll be
>>> following,
>>> > > see
>>> > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/Time+
>>> > > > > > > Based+Release+Plan
>>> > > > > > > > for an explanation.
>>> > > > > > > >
>>> > > > > > > > I've started to organize the 0.10.2.0 release, scheduled
>>> for
>>> > > > > > > mid-February,
>>> > > > > > > > here:
>>> > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/
>>> > > > > > Release+Plan+0.10.2.0
>>> > > > > > > >
>>> > > > > > > > Here are the important dates (also documented in the wiki):
>>> > > > > > > >
>>> > > > > > > > * Feature Freeze: Jan 13, 2017 (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)
>>> > > > > > > > * Code Freeze: Jan 27, 2017 (first RC created now)
>>> > > > > > > > * Release: Feb 14, 2017
>>> > > > > > > >
>>> > > > > > > > Please note that we expect these Feb releases to be a bit
>>> > lighter
>>> > > > > than
>>> > > > > > > > average because so many folks are on vacation over the
>>> winter
>>> > > > > holidays.
>>> > > > > > > > However, we still have lots of good stuff happening!
>>> > > > > > > >
>>> > > > > > > > * KIPs! We have 11 adopted with 5 already committed and 6
>>> with
>>> > > > > patches
>>> > > > > > in
>>> > > > > > > > flight. Let's plan to get all of these merged before the
>>> > feature
>>> > > > > freeze
>>> > > > > > > in
>>> > > > > > > > ~2w. Also, I did a quick pass over the VOTE threads to move
>>> > some
>>> > > > KIPs
>>> > > > > > > into
>>> > > > > > > > the adopted section. But there are some that I saw just
>>> didn't
>>> > > have
>>> > > > > > > enough
>>> > > > > > > > committer votes yet. If you have a KIP outstanding that is
>>> just
>>> > > > > waiting
>>> > > > > > > for
>>> > > > > > > > votes & already has a PR prepared, please revive the
>>> thread and
>>> > > > push
>>> > > > > it
>>> > > > > > > > through. We'll cut them off by the feature freeze, but KIPs
>>> > that
>>> > > > are
>>> > > > > > just
>>> > > > > > > > waiting on votes could still make it in.
>>> > > > > > > > * Open JIRAs. Oh my, we have a lot.
>>> > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
>>> > > > > > > > 3D%20KAFKA%20AND%20fixVersion%20%3D%200.10.2.0%20AND%
>>> > > > > > > > 20status%20not%20in%20(resolved%2C%20closed)%20ORDER%
>>> > > > > > > > 20BY%20priority%20DESC%20
>>> > > > > > > > More than 200 at the moment. I will be culling these and
>>> > cleaning
>>> > > > > them
>>> > > > > > > up,
>>> > > > > > > > although I won't remove the majority of them until we hit
>>> > feature
>>> > > > > > freeze
>>> > > > > > > > (except for cases where we know they absolutely cannot make
>>> > it).
>>> > > > Note
>>> > > > > > > that
>>> > > > > > > > if you have something you're aiming to get into 0.10.2.0,
>>> *you
>>> > > > should
>>> > > > > > > mark
>>> > > > > > > > it with that version now*.
>>> > > > > > > > * Closed JIRAs: So far ~130 closed tickets for 0.10.2.0
>>> > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
>>> > > > > > > > 3D%20KAFKA%20AND%20fixVersion%20%3D%200.10.2.0%20AND%
>>> > > > > > > > 20status%20%3D%20resolved%20OR
>>> DER%20BY%20priority%20DESC%20
>>> > > > > > > > * Release features:
>>> > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/
>>> > > > > > Release+Plan+0.10.2.0
>>> > > > > > > > has
>>> > > > > > > > a "Release Features" section that I will include with the
>>> > release
>>> > > > > > > > notes/email for the release. I've populated it with notes
>>> about
>>> > > > > > important
>>> > > > > > > > KIPs, but key bug fixes or features could also be relevant.
>>> > > Please
>>> > > > > add
>>> > > > > > to
>>> > > > > > > > this list anything you think is worth noting -- it's a
>>> struggle
>>> > > > > keeping
>>> > > > > > > up
>>> > > > > > > > with everything happening on the -dev list, so please
>>> chime in!
>>> > > > > > > >
>>> > > > > > > > I'll plan to give another update in ~1w as we get closer
>>> to the
>>> > > > > freeze
>>> > > > > > > > dates, and with increasing frequency after that.
>>> > > > > > > >
>>> > > > > > > > -Ewen
>>> > > > > > > >
>>> > > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>

--001a1145247e5f269505463b7364--