Re: [UPDATE] 0.10.1 Release Progress
Thanks, Jason! On Tue, Oct 4, 2016 at 1:57 PM, Guozhang Wang wrote: > Thanks for running the release Jason! > > On Mon, Oct 3, 2016 at 9:06 PM, Jason Gustafson > wrote: > > > Hi Everyone, > > > > The code freeze is upon us! We've made incredible progress fixing bugs > and > > improving testing. If your feature or bug fix didn't get in this time, > > don't worry since the next release will be here in a few short months. > Now > > the focus is on verifying the release candidates, the first of which will > > be cut tomorrow. Only blocking bugs or significant regressions will > result > > in new release candidates. The goal is to have a stable release by Oct. > 17. > > > > Thanks to everyone who has contributed thus far! > > > > -Jason > > > > On Tue, Sep 27, 2016 at 6:29 PM, Sriram Subramanian > > wrote: > > > > > Thanks Jason! > > > > > > On Tue, Sep 27, 2016 at 5:38 PM, Ismael Juma > wrote: > > > > > > > Thanks for the update Jason. :) > > > > > > > > Ismael > > > > > > > > On Wed, Sep 28, 2016 at 1:28 AM, Jason Gustafson > > > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > Pardon all the JIRA noise, but I've been busy reducing the scope to > > > match > > > > > the available time since we're now 6 days from the code freeze. > I've > > > > pruned > > > > > the list to about 30 tickets, some of which probably won't get in: > > > > > https://cwiki.apache.org/confluence/display/KAFKA/ > > Release+Plan+0.10.1. > > > > > Other > > > > > than a few important bug fixes which are nearing completion, the > main > > > > > remaining items are documentation improvements, additional system > > > tests, > > > > > and transient test failures. If you are looking to help out, > > addressing > > > > the > > > > > transient test failures are the biggest need since I'm sure you've > > > > noticed > > > > > all the build failures. Other than that, I think we're on track for > > the > > > > > code freeze. Keep up the great work! > > > > > > > > > > Thanks, > > > > > Jason > > > > > > > > > > On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat < > > > > > gharatmayures...@gmail.com > > > > > > wrote: > > > > > > > > > > > Great ! > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Mayuresh > > > > > > > > > > > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin < > becket@gmail.com> > > > > > wrote: > > > > > > > > > > > > > Awesome! > > > > > > > > > > > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede < > > n...@confluent.io > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Nice! > > > > > > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma < > > ism...@juma.me.uk> > > > > > > wrote: > > > > > > > > > > > > > > > > > Well done everyone. :) > > > > > > > > > > > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" < > > ja...@confluent.io> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release > > branch > > > > has > > > > > > been > > > > > > > > > > created. We're now entering the stabilization phase of > this > > > > > release > > > > > > > > which > > > > > > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > > > > > > > > > > > -Jason > > > > > > > > > > > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > > > > > > ja...@confluent.io > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on > > the > > > > > > > remaining > > > > > > > > > KIPs > > > > > > > > > > > that we are hoping to include: > > > > > > > > > > > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. > > Assuming > > > no > > > > > > > > problems > > > > > > > > > > > emerge, Ismael is planning to merge today. > > > > > > > > > > > KIP-74 (max fetch size): Review is nearing completion, > > > just a > > > > > few > > > > > > > > minor > > > > > > > > > > > issues remain. This will probably be merged tomorrow or > > > > Sunday. > > > > > > > > > > > KIP-55 (secure quotas): The patch has been rebased and > > > > probably > > > > > > > needs > > > > > > > > > one > > > > > > > > > > > more review pass before merging. Jun is confident it > can > > > get > > > > in > > > > > > > > before > > > > > > > > > > > Monday. > > > > > > > > > > > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make > it > > > in, > > > > > > we'll > > > > > > > > need > > > > > > > > > > 1) > > > > > > > > > > > some more votes on the vote thread, and 2) a few review > > > > > > iterations. > > > > > > > > > It's > > > > > > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > > > > > > > > > > > Since we are nearing the feature freeze, it would be > > > helpful > > > > if > > > > > > > > people > > > > > > > > > > > begin setting some priorities on the bugs that need to > > get > > > in > > > > > > > before > > > > > > > > > the > > > > > > > > > > > c
Re: [UPDATE] 0.10.1 Release Progress
Thanks for running the release Jason! On Mon, Oct 3, 2016 at 9:06 PM, Jason Gustafson wrote: > Hi Everyone, > > The code freeze is upon us! We've made incredible progress fixing bugs and > improving testing. If your feature or bug fix didn't get in this time, > don't worry since the next release will be here in a few short months. Now > the focus is on verifying the release candidates, the first of which will > be cut tomorrow. Only blocking bugs or significant regressions will result > in new release candidates. The goal is to have a stable release by Oct. 17. > > Thanks to everyone who has contributed thus far! > > -Jason > > On Tue, Sep 27, 2016 at 6:29 PM, Sriram Subramanian > wrote: > > > Thanks Jason! > > > > On Tue, Sep 27, 2016 at 5:38 PM, Ismael Juma wrote: > > > > > Thanks for the update Jason. :) > > > > > > Ismael > > > > > > On Wed, Sep 28, 2016 at 1:28 AM, Jason Gustafson > > > wrote: > > > > > > > Hi All, > > > > > > > > Pardon all the JIRA noise, but I've been busy reducing the scope to > > match > > > > the available time since we're now 6 days from the code freeze. I've > > > pruned > > > > the list to about 30 tickets, some of which probably won't get in: > > > > https://cwiki.apache.org/confluence/display/KAFKA/ > Release+Plan+0.10.1. > > > > Other > > > > than a few important bug fixes which are nearing completion, the main > > > > remaining items are documentation improvements, additional system > > tests, > > > > and transient test failures. If you are looking to help out, > addressing > > > the > > > > transient test failures are the biggest need since I'm sure you've > > > noticed > > > > all the build failures. Other than that, I think we're on track for > the > > > > code freeze. Keep up the great work! > > > > > > > > Thanks, > > > > Jason > > > > > > > > On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat < > > > > gharatmayures...@gmail.com > > > > > wrote: > > > > > > > > > Great ! > > > > > > > > > > Thanks, > > > > > > > > > > Mayuresh > > > > > > > > > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin > > > > wrote: > > > > > > > > > > > Awesome! > > > > > > > > > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede < > n...@confluent.io > > > > > > > > wrote: > > > > > > > > > > > > > Nice! > > > > > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma < > ism...@juma.me.uk> > > > > > wrote: > > > > > > > > > > > > > > > Well done everyone. :) > > > > > > > > > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" < > ja...@confluent.io> > > > > > wrote: > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release > branch > > > has > > > > > been > > > > > > > > > created. We're now entering the stabilization phase of this > > > > release > > > > > > > which > > > > > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > > > > > > > > > -Jason > > > > > > > > > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > > > > > ja...@confluent.io > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on > the > > > > > > remaining > > > > > > > > KIPs > > > > > > > > > > that we are hoping to include: > > > > > > > > > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. > Assuming > > no > > > > > > > problems > > > > > > > > > > emerge, Ismael is planning to merge today. > > > > > > > > > > KIP-74 (max fetch size): Review is nearing completion, > > just a > > > > few > > > > > > > minor > > > > > > > > > > issues remain. This will probably be merged tomorrow or > > > Sunday. > > > > > > > > > > KIP-55 (secure quotas): The patch has been rebased and > > > probably > > > > > > needs > > > > > > > > one > > > > > > > > > > more review pass before merging. Jun is confident it can > > get > > > in > > > > > > > before > > > > > > > > > > Monday. > > > > > > > > > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it > > in, > > > > > we'll > > > > > > > need > > > > > > > > > 1) > > > > > > > > > > some more votes on the vote thread, and 2) a few review > > > > > iterations. > > > > > > > > It's > > > > > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > > > > > > > > > Since we are nearing the feature freeze, it would be > > helpful > > > if > > > > > > > people > > > > > > > > > > begin setting some priorities on the bugs that need to > get > > in > > > > > > before > > > > > > > > the > > > > > > > > > > code freeze. I am going to make an effort to prune the > list > > > > early > > > > > > > next > > > > > > > > > > week, so if there are any critical issues you know about, > > > make > > > > > sure > > > > > > > > they > > > > > > > > > > are marked as such. > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > Jason > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Than
Re: [UPDATE] 0.10.1 Release Progress
Well done everyone! Ismael On 4 Oct 2016 5:06 am, "Jason Gustafson" wrote: > Hi Everyone, > > The code freeze is upon us! We've made incredible progress fixing bugs and > improving testing. If your feature or bug fix didn't get in this time, > don't worry since the next release will be here in a few short months. Now > the focus is on verifying the release candidates, the first of which will > be cut tomorrow. Only blocking bugs or significant regressions will result > in new release candidates. The goal is to have a stable release by Oct. 17. > > Thanks to everyone who has contributed thus far! > > -Jason > > On Tue, Sep 27, 2016 at 6:29 PM, Sriram Subramanian > wrote: > > > Thanks Jason! > > > > On Tue, Sep 27, 2016 at 5:38 PM, Ismael Juma wrote: > > > > > Thanks for the update Jason. :) > > > > > > Ismael > > > > > > On Wed, Sep 28, 2016 at 1:28 AM, Jason Gustafson > > > wrote: > > > > > > > Hi All, > > > > > > > > Pardon all the JIRA noise, but I've been busy reducing the scope to > > match > > > > the available time since we're now 6 days from the code freeze. I've > > > pruned > > > > the list to about 30 tickets, some of which probably won't get in: > > > > https://cwiki.apache.org/confluence/display/KAFKA/ > Release+Plan+0.10.1. > > > > Other > > > > than a few important bug fixes which are nearing completion, the main > > > > remaining items are documentation improvements, additional system > > tests, > > > > and transient test failures. If you are looking to help out, > addressing > > > the > > > > transient test failures are the biggest need since I'm sure you've > > > noticed > > > > all the build failures. Other than that, I think we're on track for > the > > > > code freeze. Keep up the great work! > > > > > > > > Thanks, > > > > Jason > > > > > > > > On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat < > > > > gharatmayures...@gmail.com > > > > > wrote: > > > > > > > > > Great ! > > > > > > > > > > Thanks, > > > > > > > > > > Mayuresh > > > > > > > > > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin > > > > wrote: > > > > > > > > > > > Awesome! > > > > > > > > > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede < > n...@confluent.io > > > > > > > > wrote: > > > > > > > > > > > > > Nice! > > > > > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma < > ism...@juma.me.uk> > > > > > wrote: > > > > > > > > > > > > > > > Well done everyone. :) > > > > > > > > > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" < > ja...@confluent.io> > > > > > wrote: > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release > branch > > > has > > > > > been > > > > > > > > > created. We're now entering the stabilization phase of this > > > > release > > > > > > > which > > > > > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > > > > > > > > > -Jason > > > > > > > > > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > > > > > ja...@confluent.io > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on > the > > > > > > remaining > > > > > > > > KIPs > > > > > > > > > > that we are hoping to include: > > > > > > > > > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. > Assuming > > no > > > > > > > problems > > > > > > > > > > emerge, Ismael is planning to merge today. > > > > > > > > > > KIP-74 (max fetch size): Review is nearing completion, > > just a > > > > few > > > > > > > minor > > > > > > > > > > issues remain. This will probably be merged tomorrow or > > > Sunday. > > > > > > > > > > KIP-55 (secure quotas): The patch has been rebased and > > > probably > > > > > > needs > > > > > > > > one > > > > > > > > > > more review pass before merging. Jun is confident it can > > get > > > in > > > > > > > before > > > > > > > > > > Monday. > > > > > > > > > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it > > in, > > > > > we'll > > > > > > > need > > > > > > > > > 1) > > > > > > > > > > some more votes on the vote thread, and 2) a few review > > > > > iterations. > > > > > > > > It's > > > > > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > > > > > > > > > Since we are nearing the feature freeze, it would be > > helpful > > > if > > > > > > > people > > > > > > > > > > begin setting some priorities on the bugs that need to > get > > in > > > > > > before > > > > > > > > the > > > > > > > > > > code freeze. I am going to make an effort to prune the > list > > > > early > > > > > > > next > > > > > > > > > > week, so if there are any critical issues you know about, > > > make > > > > > sure > > > > > > > > they > > > > > > > > > > are marked as such. > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > Jason > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Thanks, > > > > > > >
Re: [UPDATE] 0.10.1 Release Progress
Thanks for running the release and great to see the progress and focus on shipping a high-quality release. On Mon, Oct 3, 2016 at 9:06 PM Jason Gustafson wrote: > Hi Everyone, > > The code freeze is upon us! We've made incredible progress fixing bugs and > improving testing. If your feature or bug fix didn't get in this time, > don't worry since the next release will be here in a few short months. Now > the focus is on verifying the release candidates, the first of which will > be cut tomorrow. Only blocking bugs or significant regressions will result > in new release candidates. The goal is to have a stable release by Oct. 17. > > Thanks to everyone who has contributed thus far! > > -Jason > > On Tue, Sep 27, 2016 at 6:29 PM, Sriram Subramanian > wrote: > > > Thanks Jason! > > > > On Tue, Sep 27, 2016 at 5:38 PM, Ismael Juma wrote: > > > > > Thanks for the update Jason. :) > > > > > > Ismael > > > > > > On Wed, Sep 28, 2016 at 1:28 AM, Jason Gustafson > > > wrote: > > > > > > > Hi All, > > > > > > > > Pardon all the JIRA noise, but I've been busy reducing the scope to > > match > > > > the available time since we're now 6 days from the code freeze. I've > > > pruned > > > > the list to about 30 tickets, some of which probably won't get in: > > > > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. > > > > Other > > > > than a few important bug fixes which are nearing completion, the main > > > > remaining items are documentation improvements, additional system > > tests, > > > > and transient test failures. If you are looking to help out, > addressing > > > the > > > > transient test failures are the biggest need since I'm sure you've > > > noticed > > > > all the build failures. Other than that, I think we're on track for > the > > > > code freeze. Keep up the great work! > > > > > > > > Thanks, > > > > Jason > > > > > > > > On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat < > > > > gharatmayures...@gmail.com > > > > > wrote: > > > > > > > > > Great ! > > > > > > > > > > Thanks, > > > > > > > > > > Mayuresh > > > > > > > > > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin > > > > wrote: > > > > > > > > > > > Awesome! > > > > > > > > > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede < > n...@confluent.io > > > > > > > > wrote: > > > > > > > > > > > > > Nice! > > > > > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma < > ism...@juma.me.uk> > > > > > wrote: > > > > > > > > > > > > > > > Well done everyone. :) > > > > > > > > > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" < > ja...@confluent.io> > > > > > wrote: > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release > branch > > > has > > > > > been > > > > > > > > > created. We're now entering the stabilization phase of this > > > > release > > > > > > > which > > > > > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > > > > > > > > > -Jason > > > > > > > > > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > > > > > ja...@confluent.io > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on > the > > > > > > remaining > > > > > > > > KIPs > > > > > > > > > > that we are hoping to include: > > > > > > > > > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. > Assuming > > no > > > > > > > problems > > > > > > > > > > emerge, Ismael is planning to merge today. > > > > > > > > > > KIP-74 (max fetch size): Review is nearing completion, > > just a > > > > few > > > > > > > minor > > > > > > > > > > issues remain. This will probably be merged tomorrow or > > > Sunday. > > > > > > > > > > KIP-55 (secure quotas): The patch has been rebased and > > > probably > > > > > > needs > > > > > > > > one > > > > > > > > > > more review pass before merging. Jun is confident it can > > get > > > in > > > > > > > before > > > > > > > > > > Monday. > > > > > > > > > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it > > in, > > > > > we'll > > > > > > > need > > > > > > > > > 1) > > > > > > > > > > some more votes on the vote thread, and 2) a few review > > > > > iterations. > > > > > > > > It's > > > > > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > > > > > > > > > Since we are nearing the feature freeze, it would be > > helpful > > > if > > > > > > > people > > > > > > > > > > begin setting some priorities on the bugs that need to > get > > in > > > > > > before > > > > > > > > the > > > > > > > > > > code freeze. I am going to make an effort to prune the > list > > > > early > > > > > > > next > > > > > > > > > > week, so if there are any critical issues you know about, > > > make > > > > > sure > > > > > > > > they > > > > > > > > > > are marked as such. > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > Jason > > > > > > > > > > > >
Re: [UPDATE] 0.10.1 Release Progress
Hi Everyone, The code freeze is upon us! We've made incredible progress fixing bugs and improving testing. If your feature or bug fix didn't get in this time, don't worry since the next release will be here in a few short months. Now the focus is on verifying the release candidates, the first of which will be cut tomorrow. Only blocking bugs or significant regressions will result in new release candidates. The goal is to have a stable release by Oct. 17. Thanks to everyone who has contributed thus far! -Jason On Tue, Sep 27, 2016 at 6:29 PM, Sriram Subramanian wrote: > Thanks Jason! > > On Tue, Sep 27, 2016 at 5:38 PM, Ismael Juma wrote: > > > Thanks for the update Jason. :) > > > > Ismael > > > > On Wed, Sep 28, 2016 at 1:28 AM, Jason Gustafson > > wrote: > > > > > Hi All, > > > > > > Pardon all the JIRA noise, but I've been busy reducing the scope to > match > > > the available time since we're now 6 days from the code freeze. I've > > pruned > > > the list to about 30 tickets, some of which probably won't get in: > > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. > > > Other > > > than a few important bug fixes which are nearing completion, the main > > > remaining items are documentation improvements, additional system > tests, > > > and transient test failures. If you are looking to help out, addressing > > the > > > transient test failures are the biggest need since I'm sure you've > > noticed > > > all the build failures. Other than that, I think we're on track for the > > > code freeze. Keep up the great work! > > > > > > Thanks, > > > Jason > > > > > > On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat < > > > gharatmayures...@gmail.com > > > > wrote: > > > > > > > Great ! > > > > > > > > Thanks, > > > > > > > > Mayuresh > > > > > > > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin > > > wrote: > > > > > > > > > Awesome! > > > > > > > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede > > > > > wrote: > > > > > > > > > > > Nice! > > > > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma > > > > wrote: > > > > > > > > > > > > > Well done everyone. :) > > > > > > > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" > > > > wrote: > > > > > > > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release branch > > has > > > > been > > > > > > > > created. We're now entering the stabilization phase of this > > > release > > > > > > which > > > > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > > > > > > > -Jason > > > > > > > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > > > > ja...@confluent.io > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on the > > > > > remaining > > > > > > > KIPs > > > > > > > > > that we are hoping to include: > > > > > > > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. Assuming > no > > > > > > problems > > > > > > > > > emerge, Ismael is planning to merge today. > > > > > > > > > KIP-74 (max fetch size): Review is nearing completion, > just a > > > few > > > > > > minor > > > > > > > > > issues remain. This will probably be merged tomorrow or > > Sunday. > > > > > > > > > KIP-55 (secure quotas): The patch has been rebased and > > probably > > > > > needs > > > > > > > one > > > > > > > > > more review pass before merging. Jun is confident it can > get > > in > > > > > > before > > > > > > > > > Monday. > > > > > > > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it > in, > > > > we'll > > > > > > need > > > > > > > > 1) > > > > > > > > > some more votes on the vote thread, and 2) a few review > > > > iterations. > > > > > > > It's > > > > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > > > > > > > Since we are nearing the feature freeze, it would be > helpful > > if > > > > > > people > > > > > > > > > begin setting some priorities on the bugs that need to get > in > > > > > before > > > > > > > the > > > > > > > > > code freeze. I am going to make an effort to prune the list > > > early > > > > > > next > > > > > > > > > week, so if there are any critical issues you know about, > > make > > > > sure > > > > > > > they > > > > > > > > > are marked as such. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Jason > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Thanks, > > > > > > Neha > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > -Regards, > > > > Mayuresh R. Gharat > > > > (862) 250-7125 > > > > > > > > > >
Re: [UPDATE] 0.10.1 Release Progress
Thanks Jason! On Tue, Sep 27, 2016 at 5:38 PM, Ismael Juma wrote: > Thanks for the update Jason. :) > > Ismael > > On Wed, Sep 28, 2016 at 1:28 AM, Jason Gustafson > wrote: > > > Hi All, > > > > Pardon all the JIRA noise, but I've been busy reducing the scope to match > > the available time since we're now 6 days from the code freeze. I've > pruned > > the list to about 30 tickets, some of which probably won't get in: > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. > > Other > > than a few important bug fixes which are nearing completion, the main > > remaining items are documentation improvements, additional system tests, > > and transient test failures. If you are looking to help out, addressing > the > > transient test failures are the biggest need since I'm sure you've > noticed > > all the build failures. Other than that, I think we're on track for the > > code freeze. Keep up the great work! > > > > Thanks, > > Jason > > > > On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat < > > gharatmayures...@gmail.com > > > wrote: > > > > > Great ! > > > > > > Thanks, > > > > > > Mayuresh > > > > > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin > > wrote: > > > > > > > Awesome! > > > > > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede > > > wrote: > > > > > > > > > Nice! > > > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma > > > wrote: > > > > > > > > > > > Well done everyone. :) > > > > > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" > > > wrote: > > > > > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release branch > has > > > been > > > > > > > created. We're now entering the stabilization phase of this > > release > > > > > which > > > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > > > > > -Jason > > > > > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > > > ja...@confluent.io > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on the > > > > remaining > > > > > > KIPs > > > > > > > > that we are hoping to include: > > > > > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. Assuming no > > > > > problems > > > > > > > > emerge, Ismael is planning to merge today. > > > > > > > > KIP-74 (max fetch size): Review is nearing completion, just a > > few > > > > > minor > > > > > > > > issues remain. This will probably be merged tomorrow or > Sunday. > > > > > > > > KIP-55 (secure quotas): The patch has been rebased and > probably > > > > needs > > > > > > one > > > > > > > > more review pass before merging. Jun is confident it can get > in > > > > > before > > > > > > > > Monday. > > > > > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it in, > > > we'll > > > > > need > > > > > > > 1) > > > > > > > > some more votes on the vote thread, and 2) a few review > > > iterations. > > > > > > It's > > > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > > > > > Since we are nearing the feature freeze, it would be helpful > if > > > > > people > > > > > > > > begin setting some priorities on the bugs that need to get in > > > > before > > > > > > the > > > > > > > > code freeze. I am going to make an effort to prune the list > > early > > > > > next > > > > > > > > week, so if there are any critical issues you know about, > make > > > sure > > > > > > they > > > > > > > > are marked as such. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Jason > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Thanks, > > > > > Neha > > > > > > > > > > > > > > > > > > > > > -- > > > -Regards, > > > Mayuresh R. Gharat > > > (862) 250-7125 > > > > > >
Re: [UPDATE] 0.10.1 Release Progress
Thanks for the update Jason. :) Ismael On Wed, Sep 28, 2016 at 1:28 AM, Jason Gustafson wrote: > Hi All, > > Pardon all the JIRA noise, but I've been busy reducing the scope to match > the available time since we're now 6 days from the code freeze. I've pruned > the list to about 30 tickets, some of which probably won't get in: > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. > Other > than a few important bug fixes which are nearing completion, the main > remaining items are documentation improvements, additional system tests, > and transient test failures. If you are looking to help out, addressing the > transient test failures are the biggest need since I'm sure you've noticed > all the build failures. Other than that, I think we're on track for the > code freeze. Keep up the great work! > > Thanks, > Jason > > On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat < > gharatmayures...@gmail.com > > wrote: > > > Great ! > > > > Thanks, > > > > Mayuresh > > > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin > wrote: > > > > > Awesome! > > > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede > > wrote: > > > > > > > Nice! > > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma > > wrote: > > > > > > > > > Well done everyone. :) > > > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" > > wrote: > > > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release branch has > > been > > > > > > created. We're now entering the stabilization phase of this > release > > > > which > > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > > > -Jason > > > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > > ja...@confluent.io > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi All, > > > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on the > > > remaining > > > > > KIPs > > > > > > > that we are hoping to include: > > > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. Assuming no > > > > problems > > > > > > > emerge, Ismael is planning to merge today. > > > > > > > KIP-74 (max fetch size): Review is nearing completion, just a > few > > > > minor > > > > > > > issues remain. This will probably be merged tomorrow or Sunday. > > > > > > > KIP-55 (secure quotas): The patch has been rebased and probably > > > needs > > > > > one > > > > > > > more review pass before merging. Jun is confident it can get in > > > > before > > > > > > > Monday. > > > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it in, > > we'll > > > > need > > > > > > 1) > > > > > > > some more votes on the vote thread, and 2) a few review > > iterations. > > > > > It's > > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > > > Since we are nearing the feature freeze, it would be helpful if > > > > people > > > > > > > begin setting some priorities on the bugs that need to get in > > > before > > > > > the > > > > > > > code freeze. I am going to make an effort to prune the list > early > > > > next > > > > > > > week, so if there are any critical issues you know about, make > > sure > > > > > they > > > > > > > are marked as such. > > > > > > > > > > > > > > Thanks, > > > > > > > Jason > > > > > > > > > > > > > > > > > > > > > > -- > > > > Thanks, > > > > Neha > > > > > > > > > > > > > > > -- > > -Regards, > > Mayuresh R. Gharat > > (862) 250-7125 > > >
Re: [UPDATE] 0.10.1 Release Progress
Hi All, Pardon all the JIRA noise, but I've been busy reducing the scope to match the available time since we're now 6 days from the code freeze. I've pruned the list to about 30 tickets, some of which probably won't get in: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.1. Other than a few important bug fixes which are nearing completion, the main remaining items are documentation improvements, additional system tests, and transient test failures. If you are looking to help out, addressing the transient test failures are the biggest need since I'm sure you've noticed all the build failures. Other than that, I think we're on track for the code freeze. Keep up the great work! Thanks, Jason On Tue, Sep 20, 2016 at 3:18 PM, Mayuresh Gharat wrote: > Great ! > > Thanks, > > Mayuresh > > On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin wrote: > > > Awesome! > > > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede > wrote: > > > > > Nice! > > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma > wrote: > > > > > > > Well done everyone. :) > > > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" > wrote: > > > > > > > > > Thanks everyone for the hard work! The 0.10.1 release branch has > been > > > > > created. We're now entering the stabilization phase of this release > > > which > > > > > means we'll focus on bug fixes and testing. > > > > > > > > > > -Jason > > > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson < > ja...@confluent.io > > > > > > > > wrote: > > > > > > > > > > > Hi All, > > > > > > > > > > > > Thanks everyone for the hard work! Here's an update on the > > remaining > > > > KIPs > > > > > > that we are hoping to include: > > > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. Assuming no > > > problems > > > > > > emerge, Ismael is planning to merge today. > > > > > > KIP-74 (max fetch size): Review is nearing completion, just a few > > > minor > > > > > > issues remain. This will probably be merged tomorrow or Sunday. > > > > > > KIP-55 (secure quotas): The patch has been rebased and probably > > needs > > > > one > > > > > > more review pass before merging. Jun is confident it can get in > > > before > > > > > > Monday. > > > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it in, > we'll > > > need > > > > > 1) > > > > > > some more votes on the vote thread, and 2) a few review > iterations. > > > > It's > > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > > > Since we are nearing the feature freeze, it would be helpful if > > > people > > > > > > begin setting some priorities on the bugs that need to get in > > before > > > > the > > > > > > code freeze. I am going to make an effort to prune the list early > > > next > > > > > > week, so if there are any critical issues you know about, make > sure > > > > they > > > > > > are marked as such. > > > > > > > > > > > > Thanks, > > > > > > Jason > > > > > > > > > > > > > > > > > > -- > > > Thanks, > > > Neha > > > > > > > > > -- > -Regards, > Mayuresh R. Gharat > (862) 250-7125 >
Re: [UPDATE] 0.10.1 Release Progress
Great ! Thanks, Mayuresh On Tue, Sep 20, 2016 at 2:43 PM, Becket Qin wrote: > Awesome! > > On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede wrote: > > > Nice! > > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma wrote: > > > > > Well done everyone. :) > > > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" wrote: > > > > > > > Thanks everyone for the hard work! The 0.10.1 release branch has been > > > > created. We're now entering the stabilization phase of this release > > which > > > > means we'll focus on bug fixes and testing. > > > > > > > > -Jason > > > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson > > > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > Thanks everyone for the hard work! Here's an update on the > remaining > > > KIPs > > > > > that we are hoping to include: > > > > > > > > > > KIP-78 (clusterId): Review is basically complete. Assuming no > > problems > > > > > emerge, Ismael is planning to merge today. > > > > > KIP-74 (max fetch size): Review is nearing completion, just a few > > minor > > > > > issues remain. This will probably be merged tomorrow or Sunday. > > > > > KIP-55 (secure quotas): The patch has been rebased and probably > needs > > > one > > > > > more review pass before merging. Jun is confident it can get in > > before > > > > > Monday. > > > > > > > > > > As for KIP-79, I've made one review pass, but to make it in, we'll > > need > > > > 1) > > > > > some more votes on the vote thread, and 2) a few review iterations. > > > It's > > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > > > Since we are nearing the feature freeze, it would be helpful if > > people > > > > > begin setting some priorities on the bugs that need to get in > before > > > the > > > > > code freeze. I am going to make an effort to prune the list early > > next > > > > > week, so if there are any critical issues you know about, make sure > > > they > > > > > are marked as such. > > > > > > > > > > Thanks, > > > > > Jason > > > > > > > > > > > > > > -- > > Thanks, > > Neha > > > -- -Regards, Mayuresh R. Gharat (862) 250-7125
Re: [UPDATE] 0.10.1 Release Progress
Awesome! On Mon, Sep 19, 2016 at 11:42 PM, Neha Narkhede wrote: > Nice! > On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma wrote: > > > Well done everyone. :) > > > > On 20 Sep 2016 5:23 am, "Jason Gustafson" wrote: > > > > > Thanks everyone for the hard work! The 0.10.1 release branch has been > > > created. We're now entering the stabilization phase of this release > which > > > means we'll focus on bug fixes and testing. > > > > > > -Jason > > > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson > > > wrote: > > > > > > > Hi All, > > > > > > > > Thanks everyone for the hard work! Here's an update on the remaining > > KIPs > > > > that we are hoping to include: > > > > > > > > KIP-78 (clusterId): Review is basically complete. Assuming no > problems > > > > emerge, Ismael is planning to merge today. > > > > KIP-74 (max fetch size): Review is nearing completion, just a few > minor > > > > issues remain. This will probably be merged tomorrow or Sunday. > > > > KIP-55 (secure quotas): The patch has been rebased and probably needs > > one > > > > more review pass before merging. Jun is confident it can get in > before > > > > Monday. > > > > > > > > As for KIP-79, I've made one review pass, but to make it in, we'll > need > > > 1) > > > > some more votes on the vote thread, and 2) a few review iterations. > > It's > > > > looking a bit doubtful, but let's see how it goes! > > > > > > > > Since we are nearing the feature freeze, it would be helpful if > people > > > > begin setting some priorities on the bugs that need to get in before > > the > > > > code freeze. I am going to make an effort to prune the list early > next > > > > week, so if there are any critical issues you know about, make sure > > they > > > > are marked as such. > > > > > > > > Thanks, > > > > Jason > > > > > > > > > > -- > Thanks, > Neha >
Re: [UPDATE] 0.10.1 Release Progress
Nice! On Mon, Sep 19, 2016 at 11:33 PM Ismael Juma wrote: > Well done everyone. :) > > On 20 Sep 2016 5:23 am, "Jason Gustafson" wrote: > > > Thanks everyone for the hard work! The 0.10.1 release branch has been > > created. We're now entering the stabilization phase of this release which > > means we'll focus on bug fixes and testing. > > > > -Jason > > > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson > > wrote: > > > > > Hi All, > > > > > > Thanks everyone for the hard work! Here's an update on the remaining > KIPs > > > that we are hoping to include: > > > > > > KIP-78 (clusterId): Review is basically complete. Assuming no problems > > > emerge, Ismael is planning to merge today. > > > KIP-74 (max fetch size): Review is nearing completion, just a few minor > > > issues remain. This will probably be merged tomorrow or Sunday. > > > KIP-55 (secure quotas): The patch has been rebased and probably needs > one > > > more review pass before merging. Jun is confident it can get in before > > > Monday. > > > > > > As for KIP-79, I've made one review pass, but to make it in, we'll need > > 1) > > > some more votes on the vote thread, and 2) a few review iterations. > It's > > > looking a bit doubtful, but let's see how it goes! > > > > > > Since we are nearing the feature freeze, it would be helpful if people > > > begin setting some priorities on the bugs that need to get in before > the > > > code freeze. I am going to make an effort to prune the list early next > > > week, so if there are any critical issues you know about, make sure > they > > > are marked as such. > > > > > > Thanks, > > > Jason > > > > > > -- Thanks, Neha
Re: [UPDATE] 0.10.1 Release Progress
Well done everyone. :) On 20 Sep 2016 5:23 am, "Jason Gustafson" wrote: > Thanks everyone for the hard work! The 0.10.1 release branch has been > created. We're now entering the stabilization phase of this release which > means we'll focus on bug fixes and testing. > > -Jason > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson > wrote: > > > Hi All, > > > > Thanks everyone for the hard work! Here's an update on the remaining KIPs > > that we are hoping to include: > > > > KIP-78 (clusterId): Review is basically complete. Assuming no problems > > emerge, Ismael is planning to merge today. > > KIP-74 (max fetch size): Review is nearing completion, just a few minor > > issues remain. This will probably be merged tomorrow or Sunday. > > KIP-55 (secure quotas): The patch has been rebased and probably needs one > > more review pass before merging. Jun is confident it can get in before > > Monday. > > > > As for KIP-79, I've made one review pass, but to make it in, we'll need > 1) > > some more votes on the vote thread, and 2) a few review iterations. It's > > looking a bit doubtful, but let's see how it goes! > > > > Since we are nearing the feature freeze, it would be helpful if people > > begin setting some priorities on the bugs that need to get in before the > > code freeze. I am going to make an effort to prune the list early next > > week, so if there are any critical issues you know about, make sure they > > are marked as such. > > > > Thanks, > > Jason > > >
Re: [UPDATE] 0.10.1 Release Progress
W00t! :) On Mon, Sep 19, 2016 at 9:23 PM, Jason Gustafson wrote: > Thanks everyone for the hard work! The 0.10.1 release branch has been > created. We're now entering the stabilization phase of this release which > means we'll focus on bug fixes and testing. > > -Jason > > On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson wrote: > >> Hi All, >> >> Thanks everyone for the hard work! Here's an update on the remaining KIPs >> that we are hoping to include: >> >> KIP-78 (clusterId): Review is basically complete. Assuming no problems >> emerge, Ismael is planning to merge today. >> KIP-74 (max fetch size): Review is nearing completion, just a few minor >> issues remain. This will probably be merged tomorrow or Sunday. >> KIP-55 (secure quotas): The patch has been rebased and probably needs one >> more review pass before merging. Jun is confident it can get in before >> Monday. >> >> As for KIP-79, I've made one review pass, but to make it in, we'll need 1) >> some more votes on the vote thread, and 2) a few review iterations. It's >> looking a bit doubtful, but let's see how it goes! >> >> Since we are nearing the feature freeze, it would be helpful if people >> begin setting some priorities on the bugs that need to get in before the >> code freeze. I am going to make an effort to prune the list early next >> week, so if there are any critical issues you know about, make sure they >> are marked as such. >> >> Thanks, >> Jason >> -- Gwen Shapira Product Manager | Confluent 650.450.2760 | @gwenshap Follow us: Twitter | blog
Re: [UPDATE] 0.10.1 Release Progress
Thanks everyone for the hard work! The 0.10.1 release branch has been created. We're now entering the stabilization phase of this release which means we'll focus on bug fixes and testing. -Jason On Fri, Sep 16, 2016 at 5:00 PM, Jason Gustafson wrote: > Hi All, > > Thanks everyone for the hard work! Here's an update on the remaining KIPs > that we are hoping to include: > > KIP-78 (clusterId): Review is basically complete. Assuming no problems > emerge, Ismael is planning to merge today. > KIP-74 (max fetch size): Review is nearing completion, just a few minor > issues remain. This will probably be merged tomorrow or Sunday. > KIP-55 (secure quotas): The patch has been rebased and probably needs one > more review pass before merging. Jun is confident it can get in before > Monday. > > As for KIP-79, I've made one review pass, but to make it in, we'll need 1) > some more votes on the vote thread, and 2) a few review iterations. It's > looking a bit doubtful, but let's see how it goes! > > Since we are nearing the feature freeze, it would be helpful if people > begin setting some priorities on the bugs that need to get in before the > code freeze. I am going to make an effort to prune the list early next > week, so if there are any critical issues you know about, make sure they > are marked as such. > > Thanks, > Jason >
