+1 Thank you for taking care of the RM as well. I don't think it's the best time for me to do RM this time, sorry.
Best regards, Alexey On Tue, Feb 21, 2017 at 10:32 AM, Todd Lipcon <[email protected]> wrote: > Hi folks, > > I don't think the topic of Kudu 1.3 has been brought up on the dev list yet > (though I just hinted at it on a user@ thread). I wanted to open this > topic > to discussion by proposing a release plan. > > Back in December, the discussion around the 1.2 release was to hold off on > the security features, and push them to 1.3. So, obviously security has > been a big focus of development over the last month or so. I've been pretty > involved with this development and it seems from my perspective that the > initial phase of development (authentication without authorization) is > wrapping up, and would be good to get out to users. > > Aside from security, there are a bunch of good bug fixes and improvements. > From a quick scan of the git log, a few things of note are: > > - fixes to various cases where more disk space was consumed than actually > used for data > - support for using Breakpad for crash analysis > - new default encodings/compression to save space and increase performance > - compression of the WAL and deltafiles (performance and space) > - support for IS NULL and IS NOT NULL predicates > - improved hash-partition pruning for IN-list predicates > > ...plus a few nice bug fixes and stability improvements. > > All of the above seems like it should make for a compelling 1.3 release. > > Following the pattern of 1.2, I think we should plan to branch this week, > and then spend a week or two on stabilization and testing before making the > release candidate. > > I'll volunteer to be the RM again unles anyone else feels like taking a > turn. > > Any comments or concerns? > > -Todd > > -- > Todd Lipcon > Software Engineer, Cloudera >
