> The plan is to backport the fix and then backport removing the fix?

I'd first like to see a bit of live testing to make sure we've really fixed 
things. Then, yes, I guess the plan would be:

1. Commit this to master, 1.7.x and 1.6.x (?)
2. If Guava 15.x gets fixed, switch to that and undo these changes
3. Otherwise, get our migration to Guava 16 done and _then_ get rid of this 
stuff

Does that sound reasonable?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/261#issuecomment-33158062

Reply via email to