Can we discuss the need for 0.8.1.2? I'm wondering if it's related to the timeline of 0.8.2 in any way? For instance, if we can get 0.8.2 out in the next 2-3 weeks, do we still need to get 0.8.1.2 out or can people just upgrade to 0.8.2?
On Tue, Sep 30, 2014 at 9:53 AM, Joe Stein <joe.st...@stealth.ly> wrote: > Hi, I wanted to kick off a specific discussion on a 0.8.1.2 release. > > Here are the JIRAs I would like to propose to back port a patch (if not > already done so) and apply them to the 0.8.1 branch for a 0.8.1.2 release > > https://issues.apache.org/jira/browse/KAFKA-1502 (source jar is empty) > https://issues.apache.org/jira/browse/KAFKA-1419 (cross build for scala > 2.11) > https://issues.apache.org/jira/browse/KAFKA-1382 (Update zkVersion on > partition state update failures) > https://issues.apache.org/jira/browse/KAFKA-1490 (remove gradlew initial > setup output from source distribution) > https://issues.apache.org/jira/browse/KAFKA-1645 (some more jars in our > src > release) > > If the community and committers can comment on the patches proposed that > would be great. If I missed any bring them up or if you think any I have > proposed shouldn't be int he release bring that up too please. > > Once we have consensus on this thread my thought was that I would apply and > commit the agreed to tickets to the 0.8.1 branch. If any tickets don't > apply of course a back port patch has to happen through our standard > process (not worried about that we have some engineering cycles to > contribute to making that happen). Once that is all done, I will build > 0.8.1.2 release artifacts and call a VOTE for RC1. > > /******************************************* > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > ********************************************/ >
