Strong promises of compatibility will discourage many (breaking)
improvements, big and small. I worry about this a lot given the
existing quirky jclouds API and the large about of suboptimal API use I
observe in Stack Overflow questions and jclouds-user mails.
Thanks a lot for this, Gaul - I think this is exactly the kind of
discussion (i.e. which kind of a tradeoff are we looking for) we want
to be having here!
As far as I'm concerned, everything suggested so far is exactly that -
a suggestion - so if we feel it's not the right tradeoff to be making
at this time, let's try to come up with something else.
What would you suggestion be?
ap
PS: Also agree that the first step towards semver is "moving a number
around". But even if that doesn't affect any other development
practice, it still seems like a step in the right direction..? ;-)
