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
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.
All common PTL duties are enumerated in the PTL guide.
The Release Process for QA is documented in QA Release Process.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4