Sounds good to me. - Dan
On Fri, Sep 21, 2018 at 11:14 AM Andrew Wong <[email protected]> wrote: > I've been discussing with members of the dev community and I think it makes > sense to push out branching, to let some in-progress work finish and bake, > and to let some devs come back from time off. So I'm now proposing we > branch Monday, *Oct. 8*, and we'll vote a couple days after. > > Also, it seems other devs had plans specific to this release, so I'm happy > to hand RM duties if others want to take over. If not, I'll continue > driving it. > > Please let me know if you agree/disagree with the new plan. > > > Andrew > > On Fri, Sep 21, 2018 at 7:31 AM Andrew Wong <[email protected]> wrote: > > > Hello Kudu developers! > > > > It's been just over three months since we released 1.7.1, and it's been > > almost six months since we released 1.7.0. In that time, we've accrued > many > > important improvements and bug fixes (a whopping ~521 since Kudu 1.7.0!). > > Now seems like as good a time as any to start thinking about a Kudu 1.8.0 > > release, and I'm volunteering to RM it. > > > > I'd like to propose we cut the branch for 1.8.x on Tuesday, *Oct. 2*, > > which gives us a bit over a week to prepare, and then we'll start a vote > a > > couple of days after that. > > > > *What does this mean for you, *you ask? If this sound good to you all, > > please start thinking about and writing up release notes for notable > > changes that have landed in this release, and get them checked in before > > Oct. 2. > > > > If you're struggling to remember that far back, here's a command you can > > run to check out what you've been up to since Kudu 1.7.0's release: > > > > $ git log 472ae66565d9a8efdc81f16568249d7c4b108251..master --oneline > > --graph --no-merges --first-parent --author=<your email address> > > > > Please let me know if you agree with this plan, have comments, questions, > > concerns, etc. > > > > > > Thanks! > > Andrew > > > > > > > > >
