-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon 16 Jun 2014 10:19:40 AM MDT, Tomas Sedovic wrote: > All, > > After having proposed some changes[1][2] to > tripleo-heat-templates[3], reviewers suggested adding a deprecation > period for the merge.py script. > > While TripleO is an official OpenStack program, none of the > projects under its umbrella (including tripleo-heat-templates) have > gone through incubation and integration nor have they been shipped > with Icehouse. > > So there is no implicit compatibility guarantee and I have not > found anything about maintaining backwards compatibility neither on > the TripleO wiki page[4], tripleo-heat-template's readme[5] or > tripleo-incubator's readme[6]. > > The Release Management wiki page[7] suggests that we follow > Semantic Versioning[8], under which prior to 1.0.0 (t-h-t is ) > anything goes. According to that wiki, we are using a stronger > guarantee where we do promise to bump the minor version on > incompatible changes -- but this again suggests that we do not > promise to maintain backwards compatibility -- just that we > document whenever we break it. > > According to Robert, there are now downstreams that have shipped > things (with the implication that they don't expect things to > change without a deprecation period) so there's clearly a > disconnect here. > > If we do promise backwards compatibility, we should document it > somewhere and if we don't we should probably make that more > visible, too, so people know what to expect. > > I prefer the latter, because it will make the merge.py cleanup > easier and every published bit of information I could find suggests > that's our current stance anyway. > > Tomas > > [1]: https://review.openstack.org/#/c/99384/ [2]: > https://review.openstack.org/#/c/97939/ [3]: > https://github.com/openstack/tripleo-heat-templates [4]: > https://wiki.openstack.org/wiki/TripleO [5]: > https://github.com/openstack/tripleo-heat-templates/blob/master/README.md > > [6]: https://github.com/openstack/tripleo-incubator/blob/master/README.rst > [7]: https://wiki.openstack.org/wiki/TripleO/ReleaseManagement [8]: > http://semver.org/ > > _______________________________________________ OpenStack-dev > mailing list OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I'm going to have to agree with Tomas here. There doesn't seem to be any reasonable expectation of backwards compatibility for the reasons he outlined, despite some downstream releases that may be impacted. - -J - -- Jason E. Rist Senior Software Engineer OpenStack Management UI Red Hat, Inc. openuc: +1.972.707.6408 mobile: +1.720.256.3933 Freenode: jrist github/identi.ca: knowncitizen - -- Jason E. Rist Senior Software Engineer OpenStack Management UI Red Hat, Inc. openuc: +1.972.707.6408 mobile: +1.720.256.3933 Freenode: jrist github/identi.ca: knowncitizen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTnxutAAoJEMqxYTi6t2f4Mh4H+gOF3aUZwIxY9FSEW/Hj1EjJ eDSDDPuOwWSlMn8VNmEq44ks7KNgGDU/qpjaDUjAJ8BCEm4cXi8JtS7zYsPJJeY3 t3z/cFPkyhWLgg0qQYOB03rbqYGX58G43xa8lFjvVi7GyfqCSKJ3AxauF2bDkx+b FoQztiaHvU09dw77JmvTxPJ2CpsvBHGaLkG3NneVIBNA8WtnBqKUQrT63ZnP8K++ G98SoMSNpXlztVEnElFMZoi+Lr7rO/37kP9CvqYtXBaDgL2Wbj6B+21Pn5OUVcXd MTy0CcvvpM/P08DNFW9+coHJcQOKJSeAYuDxn8z0+bpyJkAiSf9o4zlWOWtavfU= =qXmp -----END PGP SIGNATURE----- _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
