There's an extant version incompatibility between 1.18 and 1.20 that was highlighted during the 1.19 dev cycle which is unaddressed till the unreleased 1.21 (http://pad.lv/1311227). We should treat compatibility breakage as a blocker for stable releases.
Also in addition to the api & cli, environment.jenv files need to adhere to compatibility constraints as their the only reasonable mechanism for a client to connect (credentials, certs, addresses). On Mon, Jul 28, 2014 at 10:44 AM, Curtis Hovey-Canonical < cur...@canonical.com> wrote: > Thank you everyone. > > I am glad we are promising compatibility. We are not fulling testing > minor-to-minor compatibility yet, The feature isn't even scheduled to > start yet, but we have added some tests and a lot of infrastructure to > support it. I may need to stop work on other things to deliver more of > these tests now. > > > -- > Curtis Hovey > Canonical Cloud Development and Operations > http://launchpad.net/~sinzui > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
