CONTRIBUTING.md

Installation

$ git clone https://github.com/SUSE-Enceladus/aws-regions.git
$ cd aws_regions

# Activate virtual Environment then install
# aws-regions and dev dependences in editable mode
$ pip install -e .[dev]

aws-regions is now installed in the active virtual environment in development mode.

Dev Requirements

• bumpversion

Testing Requirements

• coverage
• flake8
• pytest
• pytest-cov
• vcrpy

Contribution Checklist

• All patches must be signed. Signing Commits
• All contributed code must conform to flake8. Code Style
• All new code contributions must be accompanied by a test.
  • Tests must pass and coverage remain above 90%. Unit & Integration Tests
• Follow Semantic Versioning. Versions & Releases

Versions & Releases

aws-regions adheres to Semantic versioning; see http://semver.org/ for details.

bumpversion is used for release version management, and is configured in setup.cfg:

$ bumpversion major|minor|patch
$ git push

Bumpversion will create a commit with version updated in all locations. The annotated tag is created separately.

$ git tag -a v{version}
# git tag -a v0.0.1

# Create a message with the changes since last release and push tags.
$ git push --tags

Unit & Integration Tests

All tests should pass and test coverage should remain above 90%.

The tests and coverage can be run directly via pytest.

$ pytest --cov=aws_regions

Code Style

Source should pass flake8 and pep8 standards.

$ flake8 aws_regions tests

Signing Commits

The repository and the code base patches sent for inclusion must be GPG signed. See the GitHub article, Signing commits using GPG, for more information.