Yes, it is always wise to notify the mailing list about upcoming major changes. While not every change will bring about discussion, in those cases where there is discussion, it can reduce the need to have to rework PRs. So it is often both courteous and efficient at the same time.
On Sun, Jan 27, 2019 at 8:07 AM Remko Popma <remko.po...@gmail.com> wrote: > No objection from me, assuming that major changes are brought up on the > mailing list first. > > Remko > > > > > On Jan 27, 2019, at 3:09, Daniel.Sun <sun...@apache.org> wrote: > > > > Hi all, > > > > In order to make all major changes reviewed, I create PRs for each > > major change. And the PRs will be merged in 72 hours by default if no one > > rejects the PRs. So I am not going to add any note like "merged in 72 > hours > > if no one rejects" for each JIRA ticket and PR. > > > > If anyone objects to the lazy consensus strategy, pls let me know. > > > > Cheers, > > Daniel.Sun > > > > > > > > ----- > > Apache Groovy committer > > Blog: http://blog.sunlan.me > > Twitter: @daniel_sun > > > > -- > > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html >
