It's less about time to review than it is about being available, thinking about the change and accepting it. Especially you mention "big changes". If you can qualify what you mean by that, we can discuss. Otherwise to me it should be a no-go: reviews should be done. And, if you're blocked, sending an email to the list and asking for feedback is clearly something to do, possibly with more explanations about the why and how. And, if you get no feedback, feel free to ping.
Le dim. 27 janv. 2019 à 22:13, Daniel.Sun <sun...@apache.org> a écrit : > Luckily according to current HR of groovy core team, it's hard to archive a > big change which need more than 72 hours to review... > > > > > > ----- > Apache Groovy committer > Blog: http://blog.sunlan.me > Twitter: @daniel_sun > > -- > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html >
