[openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers
emilien at redhat.com
Fri Oct 13 22:02:10 UTC 2017
I hope we can get attention from stable-maint, release-managers and
Some projects tried hard to follow stable policy but it didn't finish
This policy is too strict for projects like installers, although it's
not a reason why the projects wouldn't be "stable".
We decided to discuss again about the tag and how it works for installers.
Proposal 1: create a new policy that fits for projects like installers.
I kicked-off something here: https://review.openstack.org/#/c/511968/
(open for feedback).
Content can be read here:
Tag created here: https://review.openstack.org/#/c/511969/ (same,
The idea is really to not touch the current stable policy and create a
new one, more "relax" that suits well for projects like installers.
Proposal 2: change the current policy and be more relax for projects
I haven't worked on this proposal while it was something I was
considering doing first, because I realized it could bring confusion
in which projects actually follow the real stable policy and the ones
who have exceptions.
That's why I thought having a dedicated tag would help to separate them.
Proposal 3: no change anywhere, projects like installer can't claim
stability etiquette (not my best option in my opinion).
Anyway, feedback is welcome, I'm now listening. If you work on Kolla,
TripleO, OpenStack-Ansible, PuppetOpenStack (or any project who has
this need), please get involved in the review process.
More information about the OpenStack-dev