Hi John,
Thanks for checking, and sorry for the delay. I'm working on it.
I'm working through some issues with the release script / my environment.
Hopefully not much longer :)
Thanks,
--Vahid
On Tue, May 7, 2019 at 10:53 AM John Roesler wrote:
> Hi Vahid,
>
> Can you let us know the status of
Hi Vahid,
Can you let us know the status of the release? I don't mean to
pressure you, but I actually just had someone ask me for a status
update on some of my bugfixes.
Thanks again for driving this!
-John
On Fri, May 3, 2019 at 5:51 PM Vahid Hashemian
wrote:
>
> Hi Sophie,
>
> Thanks for the
Hi Sophie,
Thanks for the heads-up. Once the fix is confirmed, could you please create
a ticket for it and assign it to 2.2.1 release?
Thanks,
--Vahid
On Fri, May 3, 2019 at 3:24 PM Sophie Blee-Goldman
wrote:
> Hey Vahid,
>
> We also have another minor bug fix we just uncovered and are hoping
Hey Vahid,
We also have another minor bug fix we just uncovered and are hoping to get
in today although I don't think there's a ticket for it atm...just waiting
for the build to pass.
Thanks for volunteering!
Cheers,
Sophie
On Fri, May 3, 2019 at 3:16 PM Vahid Hashemian
wrote:
> Hi John,
>
>
Hi John,
Thanks for confirming.
I'll wait for final bug fix PR for this issue to get merged so we can
safely resolve the ticket. That makes it easier with the release script.
Hopefully, the current build passes.
--Vahid
On Fri, May 3, 2019 at 3:07 PM John Roesler wrote:
> Hi Vahid,
>
> The fix
Hi Vahid,
The fix is merged to 2.2. The ticket isn't resolved yet, because the tests
failed on the 2.1 merge, but I think the 2.2.1 release is unblocked now.
Thanks,
-John
On Fri, May 3, 2019 at 10:41 AM Vahid Hashemian
wrote:
> Thanks for the filter fix and the heads up John.
> I'll wait for
Thanks for the filter fix and the heads up John.
I'll wait for that to go through then.
--Vahid
On Fri, May 3, 2019 at 8:33 AM John Roesler wrote:
> Thanks for volunteering, Vahid!
>
> I noticed that the "unresolved issues" filter on the plan page was still
> set to 2.1.1 (I fixed it).
>
> Ther
Thanks for volunteering, Vahid!
I noticed that the "unresolved issues" filter on the plan page was still
set to 2.1.1 (I fixed it).
There's one blocker left: https://issues.apache.org/jira/browse/KAFKA-8289,
but it's merged to trunk and we're cherry-picking to 2.2 today.
Thanks again!
-John
On
If there are no objections on the proposed plan, I'll start preparing the
first release candidate.
Thanks,
--Vahid
On Thu, Apr 25, 2019 at 6:27 AM Ismael Juma wrote:
> Thanks Vahid!
>
> On Wed, Apr 24, 2019 at 10:44 PM Vahid Hashemian <
> vahid.hashem...@gmail.com>
> wrote:
>
> > Hi all,
> >
>
Thanks Vahid!
On Wed, Apr 24, 2019 at 10:44 PM Vahid Hashemian
wrote:
> Hi all,
>
> I'd like to volunteer for the release manager of the 2.2.1 bug fix release.
> Kafka 2.2.0 was released on March 22, 2019.
>
> At this point, there are 29 resolved JIRA issues scheduled for inclusion in
> 2.2.1:
>
Hi all,
I'd like to volunteer for the release manager of the 2.2.1 bug fix release.
Kafka 2.2.0 was released on March 22, 2019.
At this point, there are 29 resolved JIRA issues scheduled for inclusion in
2.2.1:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%2
11 matches
Mail list logo
