Yeah, I think we're ok for the workaround with 1.7.1. Let's do that ASAP. A.
On Wed, Feb 5, 2014 at 10:58 AM, Andrew Phillips <[email protected]>wrote: > Forwarding this to the dev@ list... > > TL;DR: Fine by me if we're OK to release with a workaround and without a > fixed Guava version. > > This bug is really hurting our users. We need to stop the bleeding. Were >> constantly asking users to use a snapshot release but what we really need >> to do is give them a proper release with the workaround. >> >> I think we should do a 1.7.1 release as soon as possible. >> > > Can do, as long as we're OK with the fact that the release will contain > the workaround we had to apply. 1.7.x is still on Guava 15 and as far as I > can see the Guava team has not released a patch for that (although there > are users in the issue asking for that). > > Bumping 1.7.x to a different Guava version was "out of bounds" last I > recall, as users have complained about the previously too. > > ap >
