[release-announce] solum-tempest-plugin 0.1.0 (rocky)

no-reply at openstack.org no-reply at openstack.org
Mon Aug 20 19:28:58 UTC 2018


We are gleeful to announce the release of:

solum-tempest-plugin 0.1.0: Tempest plugin for the solum project.

This is the first release of solum-tempest-plugin. This release is
part of the rocky release series.

The source is available from:

    https://git.openstack.org/cgit/openstack/solum-tempest-plugin

Download the package from:

    https://tarballs.openstack.org/solum-tempest-plugin/

Please report issues through launchpad:

    https://bugs.launchpad.net/solum

For more details, please see below.

Changes in solum-tempest-plugin 2f068b89b7664adc490233670686cc21dca624a0..0.1.0
-------------------------------------------------------------------------------

34ce751 Remove the unused docs
bdee18c Update the README.rst file
ccb3b2a Switch to use stestr for unit test
7de42a9 Update the documentation and release notes links
dfe9791 change default python 3 env in tox to 3.5
d5ca783 fix tox python3 overrides
e5769a9 Updated from global requirements
6cac092 Updated from global requirements
e0423bc Updated from global requirements
239b07b Updated from global requirements
07ce60f Updated from global requirements
f5537c4 Remove the version test
ec4a098 Move tempest tests from solum repo to solum-tempest-plugin
f5a4836 Initial Cookiecutter Commit.




Requirements updates
--------------------

diff --git a/requirements.txt b/requirements.txt
new file mode 100644
index 0000000..6de9f4e
--- /dev/null
+++ b/requirements.txt
@@ -0,0 +1,5 @@
+# The order of packages is significant, because pip processes them in the order
+# of appearance. Changing the order has an impact on the overall integration
+# process, which may cause wedges in the gate later.
+
+pbr!=2.1.0,>=2.0.0 # Apache-2.0
diff --git a/test-requirements.txt b/test-requirements.txt
new file mode 100644
index 0000000..a9c8b03
--- /dev/null
+++ b/test-requirements.txt
@@ -0,0 +1,15 @@
+# The order of packages is significant, because pip processes them in the order
+# of appearance. Changing the order has an impact on the overall integration
+# process, which may cause wedges in the gate later.
+
+hacking<0.13,>=0.12.0 # Apache-2.0
+
+coverage!=4.4,>=4.0 # Apache-2.0
+python-subunit>=1.0.0 # Apache-2.0/BSD
+sphinx!=1.6.6,!=1.6.7,>=1.6.2 # BSD
+oslotest>=3.2.0 # Apache-2.0
+stestr>=2.0.0 # Apache-2.0
+testtools>=2.2.0 # MIT
+openstackdocstheme>=1.18.1 # Apache-2.0
+# releasenotes
+reno>=2.5.0 # Apache-2.0






More information about the Release-announce mailing list