Thank you for picking up and summarizing this thread, Andrew G!
Perhaps we did not communicate this clearly, but jclouds has had a predictable deprecation policy for at least the last three years. Users can upgrade from an earlier 1.7.x release to a later 1.7 release and breaking changes were only introduced in 1.8.0. Sometimes a given 1.7.x release contained new deprecation annotations but otherwise applications continue to work. Despite this, users choose not to upgrade to the latest micro releases.
@Everett: do you have some information you could share about challenges/complaints/other background that lead to the current suggestion?
Just from a personal perspective, that would help me try to figure out how big the relative challenges are that we're looking to balance here.
Regards ap
