Thanks Alexey for your response! Yeah, although after re-evaluated the current progress with ongoing projects such as Ranger integration with members of the dev community, I think it makes sense to push out the branching to Wednesday, *Apr. 8*. Let me know your thoughts on the new plan. Thanks a lot!
Best, Hao On Tue, Mar 24, 2020 at 4:51 PM Alexey Serbin <[email protected]> wrote: > Hi, > > Thank you Hao for taking care of the release management for 1.12 release! > > The new timeline looks good to me. Thinking about April 1st reminds > me about April Fools' Day, but since it's not a release date requiring a > public announcement, I think it's OK :) > > > Thanks > > Alexey > > On Tue, Mar 24, 2020 at 4:01 PM Hao Hao <[email protected]> > wrote: > > > After recent discussions with members of the dev community and I think it > > makes sense to push out branching further, since the in-progress work > still > > need some time to finish. So I'm now proposing a new target branch date > > which is Wednesday, *Apr. 1*, and we can re-evaluate the date if needed. > > > > Again, please let me know if you agree/disagree with the new plan. Thanks > > a lot! > > > > Best. > > Hao > > > > On Tue, Mar 17, 2020 at 1:34 PM Hao Hao <[email protected]> wrote: > > > > > Thanks Grant! > > > > > > I created the shared document to serve as a scratchpad for Kudu 1.12 > > > release > > > notes: > > > > > > > > > https://docs.google.com/document/d/1TwxsNz9vD6u6i1ihfmbHdvwQjhIiTOXABFxKnrbH08A/edit?usp=sharing > > > It contains a full list of commits since 1.11 release. If you have > > > context, please fill > > > out any notable changes that are worth adding release notes for. Also > > > feel free to > > > add anything else that you think is worth documenting. > > > > > > Also 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 such as > > > Ranger integration to finish and bake. So I'm now proposing we branch > > > Wednesday, *March. 25*, and we'll vote a couple days after. > > > > > > Please let me know if you agree/disagree with the new plan. > > > > > > Best, > > > Hao > > > > > > On Thu, Mar 12, 2020 at 8:09 AM Grant Henke > <[email protected] > > > > > > wrote: > > > > > >> The plan sounds good to me. Thank you for volunteering to RM. > > >> > > >> Could you create and share a google document similar to ones from past > > >> releases > > >> where we can start to compile the release notes? > > >> > > >> Here is an example: > > >> > > >> > > > https://docs.google.com/document/d/1CnGvoOob9H8BcY5dPciYCW5RTj9J--wXPmeMDQzqH6Y/edit?usp=sharing > > >> > > >> Thanks, > > >> Grant > > >> > > >> On Wed, Mar 11, 2020 at 11:16 PM Hao Hao <[email protected] > > > > >> wrote: > > >> > > >> > Hello Kudu developers! > > >> > > > >> > It's been a bit more than three months since we released 1.11.1. In > > that > > >> > time, we've accrued some important improvements and bug fixes > (around > > >> > 438 commits since Kudu 1.11.0). By our usual three-month release > > >> cadence, > > >> > now seems like as good a time as any to start thinking about a Kudu > > >> 1.12.0 > > >> > release, and I'm volunteering to RM it. > > >> > > > >> > I'm proposing we cut the branch for 1.12.x on Wednesday, *March 18*, > > >> > which gives us a week to prepare, and then we'll start a vote a > couple > > >> of > > >> > days after that. > > >> > > > >> > 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 March 18 2020. > > >> > > > >> > Here's a command you can run to check out roughly what you've been > up > > to > > >> > since Kudu 1.11.0 release: > > >> > > > >> > $ git log 08db97c591d9131cbef9b8e5b4f44a6e854c25f0..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! > > >> > Hao > > >> > > > >> > > >> > > >> -- > > >> Grant Henke > > >> Software Engineer | Cloudera > > >> [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke > > >> > > > > > >
