If everyone agrees about the the producer and consumer apis being fixed enough, yes, but then we should not call it 0.10.0.0 but 1.0.0.0 in my opinion. With streams just making their introduction I don't know if we are there yet.
On Mon, Mar 21, 2016 at 1:51 PM Achanta Vamsi Subhash < achanta.va...@flipkart.com> wrote: > Gerard, > > I think many people use Kafka just like any other stable software. The > producer and consumer apis are mostly fixed now and many companies across > the world are using it on production for critical use-cases. I think it is > already *expected *to work as per the theory and any bugs need to be > patched. As there is no one patching the older releases and the companies > refusing to upgrade due to the way enterprises work, can we somehow start > towards an LTS release by treating 0.10.0.0 as the LTS release to start > with? > > On Mon, Mar 21, 2016 at 4:49 PM, Gerard Klijs <gerard.kl...@dizzit.com> > wrote: > > > I think Kafka at the moment is not mature enough to support a LTS > release. > > I think it will take a lot of effort to 'guarantee' a back-port will be > > more safe to use in production then the new release. For example, when > you > > will manage the release of 0.9.0.2, with the fixes from 0.10.0.0, you > need > > to make sure all the 0.9.0.1 clients still work with it, and you don't > > introduce new bugs by the partial merge. > > I do think once there will be a 1.0.0.0 release it would be great to > have a > > lts release. > > > > On Mon, Mar 21, 2016 at 11:54 AM Achanta Vamsi Subhash < > > achanta.va...@flipkart.com> wrote: > > > > > *bump* > > > > > > Any opinions on this? > > > > > > On Mon, Mar 14, 2016 at 4:37 PM, Achanta Vamsi Subhash < > > > achanta.va...@flipkart.com> wrote: > > > > > > > Hi all, > > > > > > > > We find that there are many releases of Kafka and not all the bugs > are > > > > back ported to the older releases. Can we have a LTS (Long Term > > Support) > > > > release which can be supported for 2 years with all the bugs > > back-ported? > > > > > > > > This will be very helpful as during the last 2-3 releases, we often > > have > > > > the cases where the api of producers/consumers changes and the bugs > are > > > > only fixed in the newer components. Also, many people who are on the > > > older > > > > versions treat the latest release of that series is the stable one > and > > > end > > > > up with bugs in production. > > > > > > > > I can volunteer for the release management of the LTS release but > as a > > > > community, can we follow the rigour of back-porting the bug-fixes to > > the > > > > LTS branch? > > > > > > > > -- > > > > Regards > > > > Vamsi Subhash > > > > > > > > > > > > > > > > -- > > > Regards > > > Vamsi Subhash > > > > > > > > > -- > Regards > Vamsi Subhash >
