We have talked about the new Swift API for some years and as of today it does 
not meet my and likely others needs.  Given its slow evolution I do not have 
confidence that it will replace the old API in the next major release.  Instead 
of arguing about deprecation, perhaps we should *improve* the code so that such 
deprecation decisions will be obvious?

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

Reply via email to