kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guozhang Wang <wangg...@gmail.com>
Subject Re: [DISCUSS] Release Plan for 1.0.1
Date Tue, 16 Jan 2018 21:32:49 GMT
Hello Ewen,

Could you include one more notable changes in 1.0.1:
https://issues.apache.org/jira/browse/KAFKA-6398 ?

My PR is ready for reviews and should be mergable at any time.


Guozhang

On Tue, Jan 16, 2018 at 10:54 AM, Ewen Cheslack-Postava <ewen@confluent.io>
wrote:

> Hi all,
>
> I'd like to start the process for doing a 1.0.1 bug fix release. 1.0.0 was
> released Nov 1, 2017, and about 2.5 mos have passed and 32 bug fixes have
> accumulated so far. A few of the more notable fixes that we've merged so
> far:
>
> https://issues.apache.org/jira/browse/KAFKA-6269 - KTable restore fails
> after rebalance
> https://issues.apache.org/jira/browse/KAFKA-6185 - Selector memory leak
> with high likelihood of OOM in case of down conversion
> https://issues.apache.org/jira/browse/KAFKA-6167 - Timestamp on streams
> directory contains a colon, which is an illegal character
> https://issues.apache.org/jira/browse/KAFKA-6190 - GlobalKTable never
> finishes restoring when consuming transactional messages
> https://issues.apache.org/jira/browse/KAFKA-6252 - A fix for cleaning up
> new Connect metrics when a connector does not shut down properly
>
> These represent important fixes across all components -- core, Connect and
> Streams.
>
> I've prepared
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+1.0.1 to
> help track the fixes for 1.0.1. As you can see we have only 1 item
> currently marked as a blocker for 1.0.1. If folks with outstanding bugs
> could take a pass and a) make sure anything they think should go into 1.0.1
> is marked as such, with the appropriate priority, and b) make sure anything
> marked for 1.0.1 should really be there.
>
> Once people have taken a pass we can work on a VOTE thread and getting any
> outstanding PRs reviewed.
>
> -Ewen
>



-- 
-- Guozhang

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message