Just a quick update on the release status here: - Just pushed another rev of release notes: http://gerrit.cloudera.org:8080/3979
Please take a look and see if I described features correctly or if I missed anything. - I've been stress testing the replay cache code over the weekend and I am feeling pretty good about it. I random-inserted about 57B rows from ~240 clients into a ~70 node cluster and memory usage has stayed constant. I've also looped the integration/stress tests a few thousand times and seems reliable. So, I'm inclined to actually turn this on by default in 0.10.0. If we start seeing any issues, they'll probably be rare ones and we can have people disable it via the gflag. - Mike has put a valiant effort to finish up the delta GC stuff, but he's still looking into one particularly tricky corner of the code. Seems like we should probably defer this to the next release. - There are a few other less-risky straggling patches which we can try to get in tomorrow during the day. I'll aim to cut a release candidate in the late afternoon or evening. -Todd On Thu, Aug 11, 2016 at 6:06 AM, Jake Farrell <[email protected]> wrote: > Sounds like a good plan, +1 > > -Jake > > On Wed, Aug 10, 2016 at 5:36 PM, Todd Lipcon <[email protected]> wrote: > > > Hey Kududes and Kududettes, > > > > Back in early July, JD suggested that we do a Kudu 0.10 release in early > > August. Well, early August is here and we are rapidly approaching > > mid-August, so let's get on it :) > > > > As many of you know, JD is out of the office for a number of weeks with a > > new daughter (congrats JD!), so I'd like to volunteer to act as release > > manager for this release. Assuming folks are OK with that, here's my > > proposal: > > > > Remainder of this week > > -------------------------------- > > - we need to finish up release notes for 0.10. I just pushed a first > > draft[1] but it contains several TODOs which will need to be finished up. > > Please take a look at the notes and, if your name is mentioned, submit a > > review to add the relevant content. If your name isn't mentioned, but > > you've made a change that you think users will want to know about, please > > feel free to submit a review as well. Note: this isn't limited to > existing > > committers! All help is appreciated! > > > > - similar to the above, if you've been responsible for a new feature in > > this release, now is a good time to ensure it is well documented. > > Otherwise, all the hard work of implementing it will be for naught > > > > - straggling features: if you're working to finish up last bits of a > > feature or fix, please try to get your changes committed by Friday. I > plan > > to branch over the weekend and will be strict about changes trying to > sneak > > in during the RC voting period. > > > > Next week > > -------------- > > - I'd like to cut an initial release candidate by EOD Monday 8/15. > Assuming > > that we don't find any big issues, that should put us in good shape to > have > > the release out by EOW. > > > > Looking ahead to the next release > > ---------- > > After this release, we've achieved most of the scope items that the > > community had discussed for 1.0. Some of the items may be still > > "experimental" in 0.10 without further testing, or need some additional > > polish, but I think it's feasible to fill that gap in about a month of > > concentrated effort. That would bring us to mid-September. > > > > Conveniently, Strata/Hadoop World NYC is falling towards the end of > > September. Aligning our 1.0 release to be just before that event would be > > nice publicity for our project - if we can target the week of 9/19 for > 1.0, > > we'll be able to use the conference (9/27) as a good place to talk up > Kudu > > and pick up some new users. How do people feel about this plan? > > > > -Todd > > > > [1] https://gerrit.cloudera.org/#/c/3802/ > > > -- Todd Lipcon Software Engineer, Cloudera
