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 <ism...@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 <e...@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%20ORDER%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 > > >
