[release-announce] [monasca] monasca-ui 1.4.0 (ocata)

no-reply at openstack.org no-reply at openstack.org
Mon Dec 19 18:56:11 UTC 2016


We are excited to announce the release of:

monasca-ui 1.4.0: Monasca Plugin for Horizon

This release is part of the ocata release series.

Download the package from:

    https://tarballs.openstack.org/monasca-ui/

For more details, please see below.

Changes in monasca-ui 1.3.0..1.4.0
----------------------------------

248fab1 Fix local variable is assigned to but never used
6584d93 Remove imported but unused modules
6dc3126 Enable pep8 checks on monasca-ui
ba98874 Adjust tests for python-monascaclient >= 1.3.0
91b24ab Remove excessive print
db90acb Sync from global-requirements
e2d013f Proxy cookies from and to Kibana
c07852b Show team and repo badges on README
a7635f6 Don't include openstack/common in flake8 exclude list
7a6fca2 Remove vim header
e0cb958 Allow removing single subexpression
61fa621 Replace LOG.warn with LOG.warning
57d3ec8 TrivialFix: Remove logging import unused


Diffstat (except docs and test files)
-------------------------------------

README.md                                          |  7 +++++
monitoring/alarmdefs/constants.py                  |  2 --
monitoring/alarmdefs/forms.py                      |  2 --
monitoring/alarmdefs/panel.py                      |  2 --
monitoring/alarmdefs/tables.py                     | 12 ++------
monitoring/alarmdefs/urls.py                       |  2 --
monitoring/alarmdefs/views.py                      |  6 ++--
monitoring/alarmdefs/workflows.py                  |  2 +-
monitoring/alarms/constants.py                     |  2 --
monitoring/alarms/forms.py                         |  3 --
monitoring/alarms/panel.py                         |  2 --
monitoring/alarms/tables.py                        | 10 ++-----
monitoring/alarms/urls.py                          |  2 --
monitoring/alarms/views.py                         |  8 ++----
monitoring/api/monitor.py                          |  2 --
monitoring/dashboard.py                            |  2 --
monitoring/models.py                               |  2 --
monitoring/notifications/constants.py              |  4 +--
monitoring/notifications/forms.py                  |  2 --
monitoring/notifications/panel.py                  |  4 +--
monitoring/notifications/tables.py                 |  6 ----
monitoring/notifications/urls.py                   |  3 +-
monitoring/notifications/views.py                  |  7 +----
monitoring/overview/constants.py                   |  2 --
monitoring/overview/panel.py                       |  2 --
monitoring/overview/urls.py                        |  3 +-
monitoring/overview/views.py                       | 18 ++++++------
monitoring/static/monitoring/js/directives.js      | 14 +++++----
.../widgets/expression/expression.tpl.html         |  2 +-
monitoring/test/settings.py                        |  1 -
monitoring/test/test_data/exceptions.py            |  7 ++++-
monitoring/test/test_data/monitoring_data.py       | 12 +++++---
requirements.txt                                   |  7 +++--
setup.py                                           | 30 ++++++++++++++++++--
test-requirements.txt                              | 33 ++++++++++++----------
tox.ini                                            | 16 +++++++----
40 files changed, 124 insertions(+), 132 deletions(-)


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

diff --git a/requirements.txt b/requirements.txt
index 2e2f9e8..6b60400 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,2 +1,5 @@
-python-monascaclient
-Django<1.9,>=1.8
+# 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.
+python-monascaclient>=1.1.0 # Apache-2.0
+Django<1.9,>=1.8 # BSD
diff --git a/test-requirements.txt b/test-requirements.txt
index de56f73..32c5262 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -0,0 +1,3 @@
+# 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.
@@ -2 +5 @@
-hacking>=0.9.2,<0.10
+hacking>=0.12.0,<0.13  # Apache-2.0
@@ -4,12 +7,12 @@ hacking>=0.9.2,<0.10
-coverage>=3.6
-django-nose
-mock>=1.0
-funcsigs
-mox3>=0.7.0
-nodeenv
-nose
-nose-exclude
-nosexcover
-openstack.nose_plugin>=0.7
-nosehtmloutput>=0.0.3
-selenium
+coverage>=4.0 # Apache-2.0
+django-nose>=1.4.4 # BSD
+mock>=2.0 # BSD
+funcsigs>=0.4;python_version=='2.7' or python_version=='2.6' # Apache-2.0
+mox3>=0.7.0 # Apache-2.0
+nodeenv>=0.9.4 # BSD
+nose # LGPL
+nose-exclude # LGPL
+nosexcover # BSD
+openstack.nose-plugin>=0.7 # Apache-2.0
+nosehtmloutput>=0.0.3 # Apache-2.0
+selenium>=2.50.1 # Apache-2.0
@@ -17,2 +20,2 @@ selenium
-sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
-oslosphinx
+sphinx!=1.3b1,<1.4,>=1.2.1 # BSD
+oslosphinx>=4.7.0 # Apache-2.0





More information about the Release-announce mailing list