Jump to: navigation, search

Difference between revisions of "Translations:ReleaseNotes/Liberty/125/en"

(Importing a new version from external source)
 
(No difference)

Latest revision as of 02:06, 13 August 2016

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (ReleaseNotes/Liberty)
* Django 1.8 is now supported, and Django 1.7 is our minimum supported version (https://blueprints.launchpad.net/horizon/+spec/drop-django14-support).
* Database-backed sessions will likely not persist across upgrades due to a change in their structure (https://github.com/openstack/django_openstack_auth/commit/8c64de92f4148d85704b10ea1f7bc441db2ddfee and https://github.com/openstack/horizon/commit/ee2771ab1a855342089abe5206fc6a5071a6d99e).
* Horizon no longer uses QUnit in testing, and it has been removed from our requirements (https://blueprints.launchpad.net/horizon/+spec/replace-qunit-tests-with-jasmine).
* Horizon now has multiple configuration options for the default web URL (<code>WEBROOT</code>), static file location (<code>STATIC_ROOT</code>) and static file URL (<code>STATIC_URL</code>) in its settings files.
* Themes have moved location from <code>openstack_dashboard/static/themes</code>, to <code>openstack_dashboard/themes</code>. Paths may need to be updated accordingly. Furthermore, Horizon is aligning closer with Bootstrap markup, and themes should be built around this ideology; see the top bar and side navigation for details.
* The deprecated <code>OPENSTACK_QUANTUM_NETWORK</code> configuration option has been removed. If you still use it, replace it with <code>OPENSTACK_NEUTRON_NETWORK</code>
* There is now an <code>OPENSTACK_NOVA_EXTENSIONS_BLACKLIST</code> option in the settings, to disable selected extensions for performance reasons (https://github.com/openstack/horizon/commit/18f4b752b8653c9389f8b0471eccaa0659707ebe).
* Trove and Sahara panels now reside in <code>openstack_dashboard/contrib</code>. This is to provide separation for reviews provided mostly by the service teams. In the future, these panels may become plugins rather than being kept in Horizon (https://blueprints.launchpad.net/horizon/+spec/plugin-sanity).
* Horizon requires both a <code>volume</code> and <code>volumev2</code> endpoint for Cinder, even if only using v2.
Translation* Django 1.8 is now supported, and Django 1.7 is our minimum supported version (https://blueprints.launchpad.net/horizon/+spec/drop-django14-support).
* Database-backed sessions will likely not persist across upgrades due to a change in their structure (https://github.com/openstack/django_openstack_auth/commit/8c64de92f4148d85704b10ea1f7bc441db2ddfee and https://github.com/openstack/horizon/commit/ee2771ab1a855342089abe5206fc6a5071a6d99e).
* Horizon no longer uses QUnit in testing, and it has been removed from our requirements (https://blueprints.launchpad.net/horizon/+spec/replace-qunit-tests-with-jasmine).
* Horizon now has multiple configuration options for the default web URL (<code>WEBROOT</code>), static file location (<code>STATIC_ROOT</code>) and static file URL (<code>STATIC_URL</code>) in its settings files.
* Themes have moved location from <code>openstack_dashboard/static/themes</code>, to <code>openstack_dashboard/themes</code>. Paths may need to be updated accordingly. Furthermore, Horizon is aligning closer with Bootstrap markup, and themes should be built around this ideology; see the top bar and side navigation for details.
* The deprecated <code>OPENSTACK_QUANTUM_NETWORK</code> configuration option has been removed. If you still use it, replace it with <code>OPENSTACK_NEUTRON_NETWORK</code>
* There is now an <code>OPENSTACK_NOVA_EXTENSIONS_BLACKLIST</code> option in the settings, to disable selected extensions for performance reasons (https://github.com/openstack/horizon/commit/18f4b752b8653c9389f8b0471eccaa0659707ebe).
* Trove and Sahara panels now reside in <code>openstack_dashboard/contrib</code>. This is to provide separation for reviews provided mostly by the service teams. In the future, these panels may become plugins rather than being kept in Horizon (https://blueprints.launchpad.net/horizon/+spec/plugin-sanity).
* Horizon requires both a <code>volume</code> and <code>volumev2</code> endpoint for Cinder, even if only using v2.