On 01/31/2017 09:37 AM, Cédric Champeau wrote: > Hi guys, > > There are multiple conversations going on for weeks, and I think they > are going nowhere. We could discuss for months what's the best plan for > Groovy, without releasing anything. Here are the challenges that are > waiting for us: > > 1. release a version of Groovy that integrates Groovy macros > 2. upgrade the minimal runtime required for Groovy to 1.7, which is > required to smoothly transition to higher requirements (and also, make > our devs lives easier) > 3. upgrade the minimal runtime required for Groovy to 1.8, allowing us > to drop the old call site caching and use indy Groovy everywhere > 4. integrate Parrot, which replaces the use of Antlr2 with Antlr4 > 5. compatibility with Jigsaw, aka "Groovy as a module" > > I would like to propose the following plan: > > - Groovy 2.5: integrates 1 and 2, to be released ASAP, we've been > waiting for this for too long > - Groovy 2.6: integrate 4, implying backporting Parrot to Java 7 > - Groovy 3.0: integrate 3 and 5. The only version with necessary > breaking changes (we have no choice here) > - [ ] YES, I approve the roadmap above > - [ ] NO, I do not approve the roadmap abobe beause... > - [ ] I don't mind, or this goes beyond what I can think of
YES. Just a side note: Doing 2 in a minor release (2.4 -> 2.5) breaks backward compatibility --I'd personally rather see such changes in a major version bump. On the other hand, JRE6 is (should be) history now, so this really doesn't matter :-) -- Bahman Movaqar http://BahmanM.com - https://twitter.com/bahman__m https://github.com/bahmanm - https://gist.github.com/bahmanm PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)
signature.asc
Description: OpenPGP digital signature
