On 29 August 2017 at 06:24, Andrew Wang <andrew.w...@cloudera.com> wrote:
> So far I've seen no -1's to the branching proposal, so I plan to execute > this tomorrow unless there's further feedback. > For on going branch merge threads i.e TSv2, voting will be closing tomorrow. Does it end up in merging into trunk(3.1.0-SNAPSHOT) and branch-3.0(3.0.0-beta1-SNAPSHOT) ? If so, would you be able to wait for couple of more days before creating branch-3.0 so that TSv2 branch merge would be done directly to trunk? > > Regarding the above discussion, I think Jason and I have essentially the > same opinion. > > I hope that keeping trunk a release branch means a higher bar for merges > and code review in general. In the past, I've seen some patches committed > to trunk-only as a way of passing responsibility to a future user or > reviewer. That doesn't help anyone; patches should be committed with the > intent of running them in production. > > I'd also like to repeat the above thanks to the many, many contributors > who've helped with release improvements. Allen's work on create-release and > automated changes and release notes were essential, as was Xiao's work on > LICENSE and NOTICE files. I'm also looking forward to Marton's site > improvements, which addresses one of the remaining sore spots in the > release process. > > Things have gotten smoother with each alpha we've done over the last year, > and it's a testament to everyone's work that we have a good probability of > shipping beta and GA later this year. > > Cheers, > Andrew > >
