Quick summary.
The two blockers got resolved. We also resolved critical issue
https://issues.apache.org/jira/browse/KAFKA-7672.
We decided to move the other critical issue to 2.3:
- https://issues.apache.org/jira/browse/KAFKA-7565
We are aware of some flaky tests:
https://issues.apache.org/ji
Thanks Matthias, the list lgtm.
I will drive on merging the two PRs of
https://issues.apache.org/jira/browse/KAFKA-7672.
Guozhang
On Sat, Feb 16, 2019 at 4:11 PM Ismael Juma wrote:
> Thanks Matthias. It looks to me that we should fix all 4 issues. I would
> also suggest including the followin
Thanks Matthias. It looks to me that we should fix all 4 issues. I would
also suggest including the following trivial fix (we've seen this affect
clusters in production):
https://github.com/apache/kafka/pull/6274
I'll create a JIRA for it.
Ismael
On Sat, Feb 16, 2019 at 12:51 PM Matthias J. Sax
Hi,
yesterday was code freeze. We have two open blocker tickets atm:
- https://issues.apache.org/jira/browse/KAFKA-7920
- https://issues.apache.org/jira/browse/KAFKA-7909
Both seems to be "on track" to get resolved soon.
There is also two critical tickets:
- https://issues.apache.org/jira/b
Thanks for pointing out. It's was actually scheduled for Thursday 2/14.
I will move it to Friday 2/15 (to not cut off a day from anybody...)
-Matthias
On 2/14/19 12:17 AM, James Cheng wrote:
> Matthias,
>
> You said “Friday 2/14”, but 2/14 is this Thursday.
>
> -James
>
> Sent from my iPh
Matthias,
You said “Friday 2/14”, but 2/14 is this Thursday.
-James
Sent from my iPhone
> On Feb 11, 2019, at 2:31 PM, Matthias J. Sax wrote:
>
> Hello,
>
> this is a short reminder, that feature freeze for AK 2.2 release is end
> of this week, Friday 2/14.
>
> Currently, there are two bl
@Srinivas:
Thanks for pointing out. Missed it, because the KIP wiki page was not
updated correctly. The KIP was still listed in table "Under discussion"
instead of "Adopted". (I updated the KIP and Release Plan wiki pages
accordingly).
@Ismael: Thanks!
We also got one more blocker ticket:
- h
Hi Matthias,
I updated a few of the issues.
Ismael
On Mon, Feb 11, 2019, 2:31 PM Matthias J. Sax Hello,
>
> this is a short reminder, that feature freeze for AK 2.2 release is end
> of this week, Friday 2/14.
>
> Currently, there are two blocker issues
>
> - https://issues.apache.org/jira/brow
It seems KIP 374 is missing.
-
Srinivas
- Typed on tiny keys. pls ignore typos.{mobile app}
On Wed, 9 Jan, 2019, 05:07 Matthias J. Sax Hi all,
>
> I would like to propose a release plan (with me being release manager)
> for the next time-based feature release 2.2.0 in February.
>
> The recent K
Hello,
this is a short reminder, that feature freeze for AK 2.2 release is end
of this week, Friday 2/14.
Currently, there are two blocker issues
- https://issues.apache.org/jira/browse/KAFKA-7909
- https://issues.apache.org/jira/browse/KAFKA-7481
and five critical issues
- https://issues.a
Thanks you all!
Added 291, 379, 389, and 420 for tracking.
-Matthias
On 1/19/19 6:32 AM, Dongjin Lee wrote:
> Hi Matthias,
>
> Thank you for taking the lead. KIP-389[^1] was accepted last week[^2], so
> it seems like to be included.
>
> Thanks,
> Dongjin
>
> [^1]:
> https://cwiki.apache.org
Hi Matthias,
Thank you for taking the lead. KIP-389[^1] was accepted last week[^2], so
it seems like to be included.
Thanks,
Dongjin
[^1]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-389%3A+Introduce+a+configurable+consumer+group+size+limit
[^2]:
https://lists.apache.org/thread.html/53
KIP-379?
On Fri, 18 Jan 2019, 22:33 Matthias J. Sax Just a quick update on the release.
>
>
> We have 22 KIP atm:
>
> 81, 207, 258, 289, 313, 328, 331, 339, 341, 351, 359, 361, 367, 368,
> 371, 376, 377, 380, 386, 393, 394, 414
>
> Let me know if I missed any KIP that is targeted for 2.2 release.
I think KIP-291 is supposed to go into 2.2.0.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-291%3A+Separating+controller+connections+and+requests+from+the+data+plane
At least, according to the associated JIRA, the pull request seems to have been
merged just a couple days ago.
https://i
Thank you!
Added to the wiki page for tracking.
-Matthias
On 1/18/19 11:59 AM, Tom Bentley wrote:
> Hi Matthias,
>
> Hopefully we can get the work for KIP 183 merged too.
>
> Thanks,
>
> Tom
>
> On Fri, 18 Jan 2019, 19:33 Matthias J. Sax
>> Just a quick update on the release.
>>
>>
>> We
Hi Matthias,
Hopefully we can get the work for KIP 183 merged too.
Thanks,
Tom
On Fri, 18 Jan 2019, 19:33 Matthias J. Sax Just a quick update on the release.
>
>
> We have 22 KIP atm:
>
> 81, 207, 258, 289, 313, 328, 331, 339, 341, 351, 359, 361, 367, 368,
> 371, 376, 377, 380, 386, 393, 394,
Just a quick update on the release.
We have 22 KIP atm:
81, 207, 258, 289, 313, 328, 331, 339, 341, 351, 359, 361, 367, 368,
371, 376, 377, 380, 386, 393, 394, 414
Let me know if I missed any KIP that is targeted for 2.2 release.
21 of those KIPs are accepted, and the vote for the last one is
Thanks for volunteering Matthias! The plan sounds good to me.
Ismael
On Tue, Jan 8, 2019, 1:07 PM Matthias J. Sax Hi all,
>
> I would like to propose a release plan (with me being release manager)
> for the next time-based feature release 2.2.0 in February.
>
> The recent Kafka release history c
Hi all,
I would like to propose a release plan (with me being release manager)
for the next time-based feature release 2.2.0 in February.
The recent Kafka release history can be found at
https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan.
The release plan (with open issues and
19 matches
Mail list logo
