Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 235CC200BF3 for ; Thu, 5 Jan 2017 11:04:17 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 21DC7160B27; Thu, 5 Jan 2017 10:04:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 42341160B26 for ; Thu, 5 Jan 2017 11:04:16 +0100 (CET) Received: (qmail 75123 invoked by uid 500); 5 Jan 2017 10:04:15 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 75111 invoked by uid 99); 5 Jan 2017 10:04:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2017 10:04:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 839A818049D for ; Thu, 5 Jan 2017 10:04:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.231 X-Spam-Level: *** X-Spam-Status: No, score=3.231 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, KAM_INFOUSMEBIZ=0.75, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id l8iXgUlYe355 for ; Thu, 5 Jan 2017 10:04:10 +0000 (UTC) Received: from mail-wj0-f178.google.com (mail-wj0-f178.google.com [209.85.210.178]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E9D125F613 for ; Thu, 5 Jan 2017 10:04:09 +0000 (UTC) Received: by mail-wj0-f178.google.com with SMTP id i20so30677099wjn.2 for ; Thu, 05 Jan 2017 02:04:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=AirWvRYTVjP5EVLh6gYKjegrt1LKh1g78sG75RSCLik=; b=WXSQcGf1/EPd68Su168cGamOYU0U/o/a0PtoiXpQnoTaJOEAJrh86pGS0OlkLLbpoz p4xumo2NrsoihM/ZJWlg+CRA0URuc5Coo5ci9Ey/sRVfMtdy9BD3nhkRvEFhGsaX1aDQ nBDWUPXsitP8nPVpW3yFxFpTkL+lx9JwGam+I+oCqtUcAFNLGYi+NN9Pt1ku/jUVYyd1 uER4hOLN/sHW/cOBL9WD6FhOGRApAStRanMKg09ut2l/frcW/l87re0JSguglRQIBa0B IT2eIP6dnIx4rf39zKNctZXEWcbSQvppELWLN9ovk3H2AP+kRUD9Thx8K0jQ4X7Mwxii /HCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=AirWvRYTVjP5EVLh6gYKjegrt1LKh1g78sG75RSCLik=; b=q6ZKhJeLLA/v+OuIHe/8zzwPr0mMExqL+DrP9gg1j3vQSXvtXS5UPsJVC1lJGZq4CR KEcrFWsRk+AiukxBSWtuZFPjNhz/tqby73bbUUvL5gU3lZjFGyJXYAyAp40OBYcBHL94 Ns9mTI+19dc+Sv6a9LO/jojqcW/69jKUKr2S29cS8kLKGxeKoL+Lw/kz9w3rUSWnN0M/ yLs21/qQi20ravmOLY08oDboG5Ga27lxpuCFwu8DSBaPAMAWpM0fsJl4owV6AVd3Jevi zdT9NYvUi41P2kURtixGVSX+DD80cXs6vkEGftutToRj7+Lj+fQdduQasoIB76tC2Eyl y7Cw== X-Gm-Message-State: AIkVDXKZIcapJ/hshyQbLSWB535CUOtjbWOWJbxiU84DtfQyBs5fqyTSsEmBWu8w0Byl5d7FHQI7ffOYwF9SJg== X-Received: by 10.194.228.100 with SMTP id sh4mr47998546wjc.116.1483610644086; Thu, 05 Jan 2017 02:04:04 -0800 (PST) MIME-Version: 1.0 Sender: ismaelj@gmail.com Received: by 10.194.170.98 with HTTP; Thu, 5 Jan 2017 02:03:23 -0800 (PST) In-Reply-To: References: From: Ismael Juma Date: Thu, 5 Jan 2017 10:03:23 +0000 X-Google-Sender-Auth: OGelvgHTlhb7boi3TEMU9CRXY4A Message-ID: Subject: Re: 0.10.2.0 release planning To: dev@kafka.apache.org Content-Type: multipart/alternative; boundary=001a11369afc6d05ee0545560577 archived-at: Thu, 05 Jan 2017 10:04:17 -0000 --001a11369afc6d05ee0545560577 Content-Type: text/plain; charset=UTF-8 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 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 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 > 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 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 > > > 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 > > > 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%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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > --001a11369afc6d05ee0545560577--