Re: About the lazy consensus on Pull Requests

2019-01-28 Thread Milles, Eric (TR Tech, Content & Ops)
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

Re: About the lazy consensus on Pull Requests

2019-01-28 Thread Cédric Champeau
Ok so I think we all agree (you, me and Eric): to me a "big" change is directly related to how it impacts users. Internal refactorings that touch a lot of files are not necessarily "big" in terms of impact. Le lun. 28 janv. 2019 à 17:48, Milles, Eric (TR Tech, Content & Ops) < eric.mil...@thomsonr

Heads-up for Groovy 2.5.6

2019-01-28 Thread Paul King
Hi all, We have over 20 bug fixes on the 2_5_X branch. I'll look at preparing a new release later in the week. Now's a good time to get in any fixes you need or shout if you have something in particular that you'd like fixed in the release. PRs welcomed! :-) Cheers, Paul.