On Thu, Jul 03, 2014 at 01:14:14AM +0200, Andrew Phillips wrote: > It's been insightful for me to see two quite different opinions on > what we should be aiming for. I wonder whether we can get some data > on how/if our current rate of change is causing problems for > customers, to help guide this further?
Let's look at this another way: jclouds has a huge compatibility surface area just from its REST API against its many providers. Maintaining this is a large but valuable task which we have all contributed to over the years. I look at adding new providers, improving existing ones, and broadening the portable interfaces as our core challenges in the past and in the future. Complicating this with non-core tasks such as strong backwards compatibility guarantees, supporting many Java versions, and even Clojure support make our core tasks more difficult, especially when these tasks have dubious user value. Further we face challenges with a byzantine repository layout, racy unit tests, broken integration tests, and a backlog of pull requests. We should *streamline* our processes to allow us to deliver on our core tasks, not *burden* our development with nice-to-haves. -- Andrew Gaul http://gaul.org/
