Go to file

Sergey Kulanov 7f4bacbed0 Remove changelog section from rpm spec

Changelog is not up-to-date and we are using mechanism
for correct %changelog generation during package build,
so let's remove this section

Change-Id: I6273d8646db2037e131de44deb23185de21947e9
Related-bug: #1540325

2016-02-01 14:04:07 +02:00

fuelclient

Merge "Deprecate LISTEN_PORT parameter"

2016-01-11 15:13:06 +00:00

specs

Remove changelog section from rpm spec

2016-02-01 14:04:07 +02:00

tools

Merge "Deprecate LISTEN_PORT parameter"

2016-01-11 15:13:06 +00:00

.gitignore

Support separate jUnit files for environments

2015-08-19 16:50:25 +02:00

.gitreview

Update .gitreview for new namespace

2015-10-17 22:36:42 +00:00

.testr.conf

Generate user settings file

2015-10-20 14:27:37 +02:00

MAINTAINERS

Spec for packages MUST be reviewed by mos packaging team

2015-12-27 21:18:27 +00:00

MANIFEST.in

Generate user settings file

2015-10-20 14:27:37 +02:00

README.rst

Update link to developers' manual

2015-07-01 15:35:23 +02:00

requirements.txt

Remove argparse from requirements

2015-12-11 20:08:15 +03:00

run_tests.sh

Tox to manage all test environments on its own

2015-08-19 11:45:24 +02:00

setup.cfg

Bump version to 9.0

2015-12-17 17:11:46 +02:00

setup.py

Ensure fuel-client spec compatibility with CentOS 7

2015-12-01 15:51:30 +03:00

test-requirements.txt

Add coverage to test-requirement.txt

2015-12-11 16:25:57 +00:00

tox.ini

Fix incorrect environment variable in tox.ini

2016-01-18 08:12:41 +00:00

README.rst

python-fuelclient

python-fuelclient provides a CLI tool and a Python API wrapper for interacting with Fuel.

Project resources

Project status, bugs, and blueprints are tracked on Launchpad:: https://launchpad.net/fuel
Development documentation is hosted here:: https://docs.fuel-infra.org/fuel-dev
User guide can be found here:: http://docs.mirantis.com
Any additional information can be found on the Fuel's project wiki: https://wiki.openstack.org/wiki/Fuel

Anyone wishing to contribute to python-fuelclient should follow the general OpenStack process. A good reference for it can be found here: https://wiki.openstack.org/wiki/How_To_Contribute

http://docs.openstack.org/infra/manual/developers.html