openinfra/python-tempestconf
Code Issues Proposed changes
python-tempestconf/doc/source/contributor/contributing.rst
Martin Kopec 33f0d1e9db Fix the python 3 support and drop python 2 and 3.5 
OpenStack is dropping the py2.7 and py3.5 support in ussuri cycle.

python-tempestconf is python 3 ready and ok to drop the python 2.7
and python 3.5 support. Last python-tempestconf version officially supporting
python 2.7 and python 3.5 is 2.5.0

From now on, python-tempestconf will test all stable branches with py3
jobs.
Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html

The patch disables swift service for queens job only due to swift issues
on py3 in queens.

Story: 2007107
Task: 38163
Task: 38164

Change-Id: I0d38195f0cfbdf52a0a7e7ec721cfa9a3e2c6ea8
2020-03-02 20:51:47 +00:00

2.6 KiB
Raw Blame History

How to Contribute

python-tempestconf source code is publicly available. You can contribute code to individual projects, documentation, report bugs and vulnerabilities and request features.

Reporting Bugs

We have a storyboard project created to track any change required for python-tempestconf. If you have found any bug, please, report it there.

Important information to mention:

  • System on which the problem occurred (e.g. CentOS, Ubuntu, ...)
  • The source of python-tempestconf you have used. The package version number in case of RPM or the branch used in case of installation from git.
  • The exact command with all arguments you have used.
  • It's always better to include the console output as well.

Requesting Features

Create a story with a task for our project containing all the relevant information, mainly:

  • description of the feature
  • inputs (new CLI option, ...) and outputs (desired configuration in tempest.conf) of the feature
  • the reason why it should be implemented

Fixing bugs

  1. If you have found a bug and you know how to fix it, please, check our storyboard project for any stories which may relate to the issue. If you haven't find any related story, please, create one. Check Reporting Bugs.
  2. Follow Contributing Code and submit a code review in https://review.opendev.org/.

Contributing Code

Like any other project part of OpenStack, the development of python-tempestconf follows the OpenStack guidelines for contribution.

Learn how to contribute into OpenStack.

If you have made any changes in the source code, run tests locally before posting a review. You can do so by running tox.

If you've made any changes in the documentation (under doc/) run:

$ tox -edocs

If you've made any changes in the source code run unit tests as follows:

$ tox -epy36

and pep8 check like following:

$ tox -epep8

If you've written also a releasenote, make sure the syntax is correct by running:

$ tox -ereleasenotes

If you've made any changes which are related to a task in a story in our storyboard project, please, include a story and task number in the commit message.