openstack/validations-libs
Code Issues Proposed changes

Merge "Clarifying project branching model in CONTRIBUTING.rst"

Browse Source
This commit is contained in:
Zuul 2022-05-27 17:32:39 +00:00 committed by Gerrit Code Review
commit 79c6c886a8
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.zuul.yaml
View File

@ -62,6 +62,7 @@
- ^doc/.* - ^doc/.*
- ^README.rst - ^README.rst
- ^validations_libs/.* - ^validations_libs/.*
- ^CONTRIBUTING.rst
- validations-libs-functional - validations-libs-functional
- tripleo-ci-centos-9-undercloud-containers: &undercloud_containers_job_params - tripleo-ci-centos-9-undercloud-containers: &undercloud_containers_job_params
dependencies: dependencies:

12
CONTRIBUTING.rst
View File

@ -17,3 +17,15 @@ Pull requests submitted through GitHub will be ignored.
Validations are meant to verify functionality of tripleo systems. Validations are meant to verify functionality of tripleo systems.
Therefore a special care should be given to testing your code before submitting a review. Therefore a special care should be given to testing your code before submitting a review.
Branches and version management
===============================
Validation Framework project uses semantic versioning and derives names of stable branches
from the released minor versions. The latest minor version released is the only exception
as it is derived from the `master` branch.
Therefore, all code used by version 1.n.* of the project resides in `stable/1.n` branch,
and when version 1.(n+1) is released, new branch `stable/1.(n+1)` will be created.
By default, stable branches recieve only bug fixes and feature backports are decided on case basis
after all the necessary discussions and procedures have taken place.