Martin Kopec 47a429777c Extend single-core-review for non-functional changes

Adding a second exception for single-core-review in Devstack
repository - changes which do not affect core functionality, like
f.e. job cleanups, can be reviewed by a single core.

Change-Id: Idb6cefa510fdbfed41379eb410f4884852d1177f

2022-11-04 14:34:07 +01:00

2.3 KiB

Raw Blame History

So You Want to Contribute...

For general information on contributing to OpenStack, please check out the contributor guide to get started. It covers all the basics that are common to all OpenStack projects: the accounts you need, the basics of interacting with our Gerrit review system, how we communicate as a community, etc.

Below will cover the more project specific information you need to get started with Devstack.

Communication

IRC channel #openstack-qa at OFTC.
Mailing list (prefix subjects with [qa][devstack] for faster responses) http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss

Contacting the Core Team

Please refer to the Devstack Core Team contacts.

New Feature Planning

If you want to propose a new feature please read Feature Proposal Process Devstack features are tracked on Launchpad BP.

Task Tracking

We track our tasks in Launchpad.

Reporting a Bug

You found an issue and want to make sure we are aware of it? You can do so on Launchpad. More info about Launchpad usage can be found on OpenStack docs page

Getting Your Patch Merged

All changes proposed to the Devstack require two Code-Review +2 votes from Devstack core reviewers before one of the core reviewers can approve the patch by giving Workflow +1 vote. There are 2 exceptions, approving patches to unblock the gate and patches that do not relate to the Devstack's core logic, like for example old job cleanups, can be approved by single core reviewers.

Project Team Lead Duties

All common PTL duties are enumerated in the PTL guide.

The Release Process for QA is documented in QA Release Process.

2.3 KiB Raw Blame History