The normal practice is to mark the related Jira issue(s) with a 'breaking' label. We sometimes don't do that if the previous behavior was deemed a bug. In any case, I have marked both the relevant issues with the label now. I also updated the release notes to list those two issues under breaking changes; they should appear next time the website is re-built.Cheers, Paul.On Thu, Jun 8, 2017 at 10:43 PM, Winnebeck, Jason <Jason.Winnebeck@windstream.
com> wrote:I see there is Elvis support for Optional, which is pretty cool.
But when there are breaking changes like this that affect runtime behavior without a change in code, is there a place where this is documented when the release comes out? It would be a nice section to include for Groovy 2.5 documentation a list of breaking changes so you can find any issues in code.
This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.
From: Jochen Theodorou [mailto:firstname.lastname@example.org]
Sent: Tuesday, June 06, 2017 7:45 AM
To: email@example.com; firstname.lastname@example.org
Subject: Groovy 2.5.0-beta-1 released
The Apache Groovy team is pleased to announce version 2.5.0-beta-1 of Apache Groovy.
Apache Groovy is a multi-facet programming language for the JVM.
Further details can be found at the http://groovy.apache.org website.
This is a pre-release of a new version of Groovy.
We greatly appreciate any feedback you can give us when using this version.
This release includes 8 bug fixes/improvements as outlined in the changelog:
Sources can be downloaded from: http://www.groovy-lang.org/dow
Convenience binaries, SDK and documentation can be found at:
Jars are also available within the major binary repositories.
We would like to thank all people who contributed to this release.
We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at https://groovy.apache.org/
The Apache Groovy team.