We are planning on supporting 0.8.2 upgrades too. We already have KAFKA-3188 and KAFKA-3201 for the tests. Do you think they are incomplete?
On Mon, Mar 7, 2016 at 5:15 PM, Ashish Singh <asi...@cloudera.com> wrote: > +1 (non-binding) > > My understanding is that we decided to support upgrading from 08.2.x to > 0.10.0.0 as well, due to short release cycle. Please correct me if that is > not true. Created KAFKA-3348 and KAFKA-3349 to add tests for making sure > following paths work fine. > > 1. 0.8.2.x -> 0.10.0.0 > 2. 0.9.1.x -> 0.10.0.0 > > > On Mon, Mar 7, 2016 at 5:04 PM, Gwen Shapira <g...@confluent.io> wrote: > >> Important clarification: >> >> In order to keep the release quality up to the usual Kafka standards, >> we will want to only commit tested features. >> >> When deciding on whether to push your feature into 0.10.0 or delay to >> the next release, please take into account whether you'll have time to >> complete the system tests for the feature and not just the basic code. >> >> Gwen >> >> On Mon, Mar 7, 2016 at 4:53 PM, Gwen Shapira <g...@confluent.io> wrote: >> > In order to track the many KIPs that we are trying to land in the next >> > two weeks, I created this page: >> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.10.0 >> > >> > There are a lot of KIPs under discussion and not too much time to >> > finalize all of them. Lets do our best to review, discuss and vote on >> > the KIPs, so the developers will have a chance of getting a patch in >> > on time. >> > >> > Gwen >> > >> > On Mon, Mar 7, 2016 at 4:46 PM, Becket Qin <becket....@gmail.com> wrote: >> >> +1 (non-binding) >> >> >> >> BTW, if possible, I would like to have KIP-33 in 0.10.0 to solve the >> long >> >> pending retention issue. >> >> >> >> On Mon, Mar 7, 2016 at 3:26 PM, Joel Koshy <jjkosh...@gmail.com> wrote: >> >> >> >>> +1 >> >>> >> >>> On Mon, Mar 7, 2016 at 9:27 AM, Gwen Shapira <g...@confluent.io> >> wrote: >> >>> >> >>> > Greetings Kafka Developer Community, >> >>> > >> >>> > As you all know, we have few big features that are almost complete >> >>> > (Timestamps! Interceptors! Streams!). It is time to start planning >> our >> >>> > next release. >> >>> > >> >>> > I suggest the following: >> >>> > * Cut branches on March 21st >> >>> > * Publish the first release candidate the next day >> >>> > * Start testing, finding important issues, fixing them, rolling out >> new >> >>> > releases >> >>> > * And eventually get a release candidate that we all agree is awesome >> >>> > enough to release. Hopefully this won't take too many iterations :) >> >>> > >> >>> > Note that this is a 2 weeks heads-up on branch cutting. After we cut >> >>> > branches, we will try to minimize cherrypicks to just critical bugs >> >>> > (because last major release was a bit insane). >> >>> > Therefore, if you have a feature that you really want to see in >> >>> > 0.10.0 - you'll need to have it committed by March 21st. As a curtesy >> >>> > to the release manager, if you have features that you are not >> planning >> >>> > on getting in for 0.10.0, please change the "fix version" field in >> >>> > JIRA accordingly. >> >>> > >> >>> > I will send a heads-up few days before cutting branches, to give >> >>> > everyone a chance to get stragglers in. >> >>> > >> >>> > The vote will be open for 72 hours. >> >>> > All in favor, please reply with +1. >> >>> > >> >>> > Gwen Shapira >> >>> > >> >>> >> > > > > -- > > Regards, > Ashish
