Went through the list and cleaned it up. Most patches just need a final review. The only JIRA that has no patch is https://issues.apache.org/jira/browse/KAFKA-1723.
On Fri, Dec 26, 2014 at 2:18 PM, Gwen Shapira <gshap...@cloudera.com> wrote: > Actually, KAFKA-1785 <https://issues.apache.org/jira/browse/KAFKA-1785> > can > also wait - since it is likely to be part of a larger patch. > > On Thu, Dec 25, 2014 at 10:39 AM, Gwen Shapira <gshap...@cloudera.com> > wrote: > > > IMO: > > KAFKA-1790 - can be pushed out (or even marked as "won't fix") > > KAFKA-1782 - can be pushed out (not really a blocker) > > > > The rest look like actual blockers to me. > > > > Gwen > > > > On Tue, Dec 23, 2014 at 1:32 PM, Otis Gospodnetic < > > otis.gospodne...@gmail.com> wrote: > > > >> Hi, > >> > >> I see 16 open issues for 0.8.2 at > >> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20fixVersion%20%3D%200.8.2%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20DESC%2C%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > >> - some with patches, some blockers, some blockers without patches. > >> > >> Are all issues listed as blockers truly blockers for 0.8.2? > >> > >> Thanks, > >> Otis > >> -- > >> Monitoring * Alerting * Anomaly Detection * Centralized Log Management > >> Solr & Elasticsearch Support * http://sematext.com/ > >> > >> > >> On Mon, Dec 1, 2014 at 8:13 PM, Joe Stein <joe.st...@stealth.ly> wrote: > >> > >> > If we can have a build ready by Dec 26th I think that is feasible. I > >> could > >> > prepare and post that if we think we have the votes and a stable > >> version. > >> > > >> > /******************************************* > >> > Joe Stein > >> > Founder, Principal Consultant > >> > Big Data Open Source Security LLC > >> > http://www.stealth.ly > >> > Twitter: @allthingshadoop > >> > ********************************************/ > >> > On Dec 1, 2014 7:56 PM, "Neha Narkhede" <neha.narkh...@gmail.com> > >> wrote: > >> > > >> > > +1 for doing a 0.8.2 final before the December break. > >> > > > >> > > On Mon, Dec 1, 2014 at 8:40 AM, Jun Rao <jun...@gmail.com> wrote: > >> > > > >> > > > We are currently discussing a last-minute API change to the new > java > >> > > > producer. We have also accumulated a few more 0.8.2 blockers. > >> > > > > >> > > > > >> > > > > >> > > > >> > > >> > https://issues.apache.org/jira/browse/KAFKA-1642?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%200.8.2 > >> > > > > >> > > > So, we likely will have another 0.8.2 release in Dec. However, I > am > >> not > >> > > > sure if that's beta2 or final. > >> > > > > >> > > > Thanks, > >> > > > > >> > > > Jun > >> > > > > >> > > > On Wed, Nov 26, 2014 at 12:22 PM, Otis Gospodnetic < > >> > > > otis.gospodne...@gmail.com> wrote: > >> > > > > >> > > > > Hi, > >> > > > > > >> > > > > People using SPM to monitor Kafka have been anxiously asking us > >> about > >> > > the > >> > > > > 0.8.2 release and we've been telling them December. Is that > still > >> > the > >> > > > > plan? > >> > > > > > >> > > > > Thanks, > >> > > > > Otis > >> > > > > -- > >> > > > > Monitoring * Alerting * Anomaly Detection * Centralized Log > >> > Management > >> > > > > Solr & Elasticsearch Support * http://sematext.com/ > >> > > > > > >> > > > > >> > > > >> > > >> > > > > > -- Thanks, Neha
