Many of those won't merge cleanly - I had tried a few already but I'll see what can be done.
On Tue, Nov 12, 2019 at 1:35 AM Milles, Eric (TR Tech, Content & Ops) < eric.mil...@thomsonreuters.com> wrote: > I know this seems like a lot to ask for 2.5.9, but I scanned the commits > in master and there are individual commits tagged with the following bug > fixes: > > GROOVY-7722 > GROOVY-8372 > GROOVY-8305 > GROOVY-8507, GROOVY-9301 > GROOVY-8457 > GROOVY-9257 > GROOVY-9195 > GROOVY-9127 > GROOVY-9294 > GROOVY-7996 > GROOVY-6996 > GROOVY-9266 > GROOVY-9244 > GROOVY-9270 > GROOVY-9240 > GROOVY-9229, GROOVY-9233 > > If any particular commit does not merge cleanly, I could help backport or > evaluate if it should be excluded. > > ------------------------------ > *From:* Paul King <pa...@asert.com.au> > *Sent:* Monday, November 11, 2019 12:21 AM > *To:* Groovy_Developers <dev@groovy.apache.org> > *Subject:* Upcoming releases > > > We plan to do a RC-2 release shortly (possibly next week) and it's > probably also time for releases on other branches. The 2.5 branch has > numerous fixes. The 2.4 branch is nominally unsupported but we have been > asked to do another release to get some key fixes onto that branch. And an > alpha of 4.0 is also on the cards. > > Please let us know if there are specific fixes you want for any of those > releases. > > Cheers, Paul. > >
