Thanks Gwen!

One thing that I forgot to mention during the meeting is that we need to
create a KIP for another producer API change also (KAFKA-1660). The code is
almost ready and we just need to figure out some details about interacting
with concurrent flush() calls.

Guozhang

On Tue, Mar 3, 2015 at 12:12 PM, Gwen Shapira <gshap...@cloudera.com> wrote:

> Hi,
>
> I put together a (very) short summary of the discussion and decisions:
>
> KIPs:
> We reviewed the list of KIPs posted here:
>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
>
> * KIP-2: Ready for formal vote
> * KIP-3: Discussion closed. There’s a new KIP (14) for standardizing
> command line options.
> * KIP-4: Need to think about and document APIs in detail, update KIP
> and discuss.
> * KIP-5: Need some fleshing out in the KIP - open questions about how
> exactly it will be used
> * KIP-6: Everyone should go back to review the KIP.
> * KIP-7:  Ready for vote
> * KIP-12: Sriharsha will put in a blueprint for discussion
> * KIP-13: Need more discussion in mailing list about specific details
>
> * Ewen had good suggestion on how to fix the port binding in tests.
> * Create KIP to remove JDK6 support
>
> Gwen
>



-- 
-- Guozhang

Reply via email to