I suggested releasing the hack in 2.1.0 to provide a "deprecation/transition release". That 2.1.0, IMO, could be released as soon as we are able to deliver it. Next release would drop support for 16 and 17, and we can plan its release date as appropriate.
On 31 March 2017 at 20:17, Andrew Phillips <aphill...@qrmedia.com> wrote: >> Why not move directly to Guava 18 in 2.1.0? > > > I'm not sure what timeline we have in mind for this, but would that perhaps > be rather short notice? Do we have a rough release date in mind for 2.1.0? > > Regards > > ap
