Difference between revisions of "Puppet/Backport policy"
< Puppet
(retire page) |
|||
| Line 1: | Line 1: | ||
| + | '''These docs are outdated, but kept here for historical reasons and search access. To view the latest docs, please refer to http://docs.openstack.org/developer/puppet-openstack-guide/''' | ||
| + | |||
| + | <strike> | ||
This page documents Puppet OpenStack backport policy. | This page documents Puppet OpenStack backport policy. | ||
| Line 12: | Line 15: | ||
* Explain in commit message what is conflicting and how it's resolved. | * Explain in commit message what is conflicting and how it's resolved. | ||
* Document the changes between master and stable branches in the code or in the commit message. | * Document the changes between master and stable branches in the code or in the commit message. | ||
| + | </strike> | ||
Latest revision as of 23:30, 18 May 2016
These docs are outdated, but kept here for historical reasons and search access. To view the latest docs, please refer to http://docs.openstack.org/developer/puppet-openstack-guide/
This page documents Puppet OpenStack backport policy.
Can be backported
- Critical and High bugs fixes, if reported in Launchpad.
- Features if they don't change anything in the stable interface and only if backward compatibility is fully respected. Also if the feature works for the OpenStack release where it's backported to.
Cannot be backported
- Medium and Low bug fixes
- Features that break backward compatibility or change the existing interface (default values or name of parameters).
Merge Conflict
- Explain in commit message what is conflicting and how it's resolved.
- Document the changes between master and stable branches in the code or in the commit message.
