I am +1 on a 0.8.1.1 release ( off the 0.8.1 branch tagged) for blocking bug fixes. If we have features/improvements for 0.8.2 then we should hold them off ( with 0.9.0 providing more system changes).
/******************************************* Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop ********************************************/ > On Mar 18, 2014, at 8:11 PM, Otis Gospodnetic <otis.gospodne...@gmail.com> > wrote: > > Hi, > > We are in the process of migrating to 0.8.1, so we haven't seen any bugs > yet, but would welcome a bugfix release if others are reporting issues. > Versioning Q: wouldn't that be 0.8.2? > > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > > > On Tue, Mar 18, 2014 at 8:56 PM, Neha Narkhede <neha.narkh...@gmail.com>wrote: > >> Thanks for giving the 0.8.1 release a spin! A few people have reported bugs >> with delete topic <https://issues.apache.org/jira/browse/KAFKA-1310> and >> also the automatic leader >> rebalancing<https://issues.apache.org/jira/browse/KAFKA-1305>feature >> that we released as part of 0.8.1. These features were released as >> beta and were not widely tested at LinkedIn, unlike most of the stuff that >> we have released in the past. As a result, more bugs are being reported on >> 0.8.1 that are of a rather serious nature. It is unclear how many of these >> bugs might show up on 0.8.1 as more people adopt it. To mitigate the impact >> and also to continue releasing stable code to our users, I'm proposing we >> do a point release (0.8.1.1?) to turn off these features for the time >> being. Stabilize and test these and then release these as part of 0.8.2. >> >> Do people have any thoughts on this? >> >> Thanks, >> Neha >>
