Hi everyone, Last week at the Technical Committee meeting, following the discussion on this mailing-list a few weeks ago, we finally passed a definition[1] for a standard base deprecation policy for OpenStack projects.
[1] http://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html This is expressed as a tag that project teams can choose to add to specific deliverables that they produce, to assert that they will follow (at the very least) this base deprecation policy when it comes to removing features or configuration options in that project. It is meant to convey that minimal insurance to downstream consumers of that project. It's worth noting that it's completely fine for a given deliverable to *not* assert that. Complying with this policy has a cost, as it forces a time-constrained process and imposes to maintain features in the code during the deprecation period, distracting useful resources from pure development. Young or fast-moving projects may not be able or willing to slow down and to pay that cost at this stage of their development. This tag requires a certain maturity and stability which some projects have just not reached yet. If you want to assert that a service your team delivers will, starting with their Liberty release, follow that base deprecation policy, you can propose a change adding that tag to the corresponding deliverable in the reference/projects.yaml file in the openstack/governance repository. Thanks in advance! -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
