OK, given it's not a regression does anyone strongly oppose moving forward with 1.1.0 and try to squeeze 1.1.1 in in a couple weeks? In general my philosophy is that each release should be at least as stable as previous ones, but if we get into the habit of blocking releases because there's one more bug found that's not in the release, then it will be hard to keep our schedules.
If no one -1s before tomorrow morning I'll close the vote and post the release probably by mid-afternoon tomorrow PST. -Todd On Thu, Nov 17, 2016 at 8:26 PM, Jordan Birdsell <[email protected]> wrote: > Agreed with proceeding and doing a 1.1.1 release. > > On Thu, Nov 17, 2016, 5:11 PM Dan Burkert <[email protected]> wrote: > > > Not a regression, it's been there since the add/drop range partitions > > feature landed. > > > > - Dan > > > > On Thu, Nov 17, 2016 at 4:58 PM, Todd Lipcon <[email protected]> wrote: > > > > > Sorry for radio silence on the vote thread so far -- been traveling > this > > > week. > > > > > > Is the range partition bug a regression or also present in 1.0? If it's > > not > > > a regression i think it's reasonable to continue with the release and > try > > > to fix in a 1.1.1 along with a couple other late discovered bugs. > > > > > > Todd > > > > > > On Nov 17, 2016 6:50 PM, "Dan Burkert" <[email protected]> wrote: > > > > > > Dimitris Tsirogiannis just uncovered a bug that allows unintended > range > > > partitions to be dropped: KUDU-1750 > > > <https://issues.apache.org/jira/browse/KUDU-1750>. The bug allows a > > range > > > partition to be dropped if either the lower or upper bound range > > partition > > > key matches, instead of requiring both to match (it boils down to an || > > > where an && ought to be). I'm not sure whether this is high priority > > > enough to sink the vote, but we should consider it. This could be > > > construed as 'unintended data loss if the API is not used carefully'. > > Fix > > > is in review. > > > > > > - Dan > > > > > > On Thu, Nov 17, 2016 at 11:58 AM, Brock Noland <[email protected]> > wrote: > > > > > > > +1 (non-binding) > > > > > > > > Built on 7.2 and ran tests > > > > > > > > On Monday, November 14, 2016, Todd Lipcon <[email protected]> wrote: > > > > > > > > > Hi, > > > > > > > > > > The Apache Kudu team is happy to announce the first release > candidate > > > for > > > > > Apache Kudu 1.1.0. > > > > > > > > > > Apache Kudu 1.1 is a minor release which adds various new features, > > > > > improvements, bug fixes, and optimizations on top of Kudu 1.0. > Please > > > see > > > > > the release notes for details. > > > > > > > > > > The is a source-only release. The artifacts were staged here: > > > > > https://dist.apache.org/repos/dist/dev/kudu/1.1.0-RC1/ > > > > > > > > > > Java convenience binaries in the form of a Maven repository are > > staged > > > > > here: > > > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1005/ > > > > > > > > > > It was built from this tag: > > > > > https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h= > > > > > 3f64b68724ded320a31b69467c5a5f7744b07a50 > > > > > > > > > > The release notes can be found here (some links from this document > > will > > > > > only work when this version is released): > > > > > https://github.com/apache/kudu/blob/branch-1.1.x/docs/ > > > release_notes.adoc > > > > > > > > > > KEYS file: > > > > > http://www.apache.org/dist/kudu/KEYS > > > > > > > > > > I'd suggest going through the README, building Kudu, and running > the > > > > > unit tests. Testing out the Maven repo would also be appreciated. > > > > > > > > > > While voting, please note that there are some known test failures > on > > > RHEL > > > > > 6: > > > > > - sasl_rpc-test fails in ASAN builds due to a memory leak in > > libkrb5.so > > > > > - external_mini_cluster-test fails in RELEASE builds due to a bug > in > > > MIT > > > > > Kerberos 1.10 (the workaround is in progress) > > > > > These are test-only issues related to in-progress security work > which > > > is > > > > > not yet supported in Kudu 1.1. Please disregard such failures when > > > > voting. > > > > > > > > > > Please try the release and vote; the vote will end in 72 hours (on > > > > > 11/17/2016 at 4:30pm PST). > > > > > > > > > > Thanks, > > > > > Todd > > > > > > > > > > > > > > > -- Todd Lipcon Software Engineer, Cloudera
