I concur. I suspect people/organizations who are doing CD *probably* won't mind such a change as much as the people who use the versioned releases will mind backwards-incompatibility. Correct me if I'm wrong, but doing CD requires a certain willingness to roll with the punches, so to speak, whereas people using versioned releases are less likely to be as flexible.
Best Regards, Solly Ross ----- Original Message ----- From: "Thierry Carrez" <thie...@openstack.org> To: openstack-dev@lists.openstack.org Sent: Thursday, March 20, 2014 6:51:26 AM Subject: Re: [openstack-dev] [nova] Backwards incompatible API changes Christopher Yeoh wrote: > The patch was merged in October (just after Icehouse opened) and so has > been used in clouds that do CD for quite a while. After some discussion > on IRC I think we'll end up having to leave this backwards incompatible > change in there - given there are most likely users who now rely on > both sets of behaviour there is no good way to get out of this > situation. I've added a note to the Icehouse release notes. I still think reverting before release is an option we should consider. My point is, yes we broke it back in October for people doing CD (and they might by now have gotten used to it), if we let this to release we'll then break it for everyone else. We put a high emphasis into guaranteeing backward compatibility between releases. I think there would be more damage done if we let this sail to release, compared to the damage of reverting CD followers to pre-October behavior... -- Thierry Carrez (ttx) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
