python-glareclient 0.5.3 Release

Marker is required to get the next page in list api
in case there are more records available either because of
custom limit provided in request or because of default limit
configured in system (client and server).

ex: glare list all --limit=5 --marker=<artifact_id>

Change-Id: I9f5c890c46b7f1f1e6fefdb7320c4fe00a2b0972
Closes-bug: #1755995

This reverts commit 9d9fbb67.

This was only needed for Python < 2.7, but glareeclient's setup.cfg
already declares compatibility only with 2.7.

Change-Id: I2975485d884df08494189c4f4d598b44d9c5abd8

Glare Client v0.5.2

In change Ic0762f7a379754d19147a4f41a6d5a98abdc86b0
we renamed <type_name> section to unified 'artifacts'.

We need to reflect this changes in the client, otherwise
it doesn't work.

Change-Id: I10e5b5678180586d6f09b8dd4d83fb3f45e1f569

Now to sort list of artifacts by some field cli accepts
-s option. Unfortunatelly this option appeared in openstack
client and we have to remane ours.

By tradition we use capital letters for conflicting options,
therefore we should rename -s to -S.

Change-Id: Ic1ab7f28112f04e21ed3d6e3a018c5fc5d44e314

Now when user requests a list of artifacts glare returns
a json dict that has a section called after the type name,
which contains the list of the artifacts.
Example:
GET /artifacts/my_artifacts

{"my_artifacts": [...]}

It's not really a resful approach, so it's suggested to create a
unified section 'artifacts' for all cases, i.e. return
{"artifacts": [...]}

Change-Id: I2afb80fc7285bb8111a45a88d03f8ea21052f871

We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.

This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.

Change-Id: I57b7cb9aff05f4f81f02b39b603f3480943f914e

Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.

Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.

This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.

Change-Id: Ib3988b96b3bfd6b200dc5e746797aef098a33ce0

Change-Id: Id15eb5a248faf916cc6e8378c76f7e34836cbe2c

Change-Id: I7326cae290546a3c2d1ce9a6823f0936330c55d5