groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milles, Eric (TR Tech, Content & Ops)" <>
Subject Re: About the lazy consensus on Pull Requests
Date Mon, 28 Jan 2019 16:47:01 GMT
I think "big" refers to impact to users of the language, not number of files/lines touched.
 Let's say you change copyright notices; that will affect a lot of files but not a lot of
users.  Changes like altering the jars structure, how the static type checker works, new language
syntax, making compile static on by default are examples of "big changes" that will impact

Another example, let's say I want to make "indy" the new default and get rid of the separate
classified jars.  This is a big change since many, many users are not using the indy jars
and so they would likely experience some difference in compilation or execution, even though
all the same class files are delivered in the jars.

From: Daniel.Sun <>
Sent: Sunday, January 27, 2019 3:46 PM
Subject: Re: About the lazy consensus on Pull Requests

Let's have a look at some examples to clarify the "big changes":

1) Removing unnecessary boxing and unboxing modifies a lot of files, it is a
big change but it is just a refactoring, so I think it can apply the lazy
consensus strategy.

2) Supporting switch expression of Java 12 will impact groovy users, it is a
big change and can not apply the lazy consensus strategy.

Agree with me?


Apache Groovy committer
Twitter: @daniel_sun

Sent from:

View raw message