Senlin Dashboard Release Notes - en to en_GB translation catalogue (10 entries)

en: Angular-based panels are made as default. New features will not be added into Django-based panels anymore. And Django-based panels will be removed after S cycle or later.
en_GB: Angular-based panels are made as default. New features will not be added into Django-based panels any more. And Django-based panels will be removed after S cycle or later.

en: Python 2.7 support has been dropped. Last release of senlin-dashboard to support python 2.7 is OpenStack Train. The minimum version of Python now supported by senlin-dashboard is Python 3.6.
en_GB: Python 2.7 support has been dropped. Last release of Senlin-dashboard to support Python 2.7 is OpenStack Train. The minimum version of Python now supported by Senlin-dashboard is Python 3.6.

en: Scale-in and Scale-out actions for cluster added. These actions are added as row action for each cluster in Clusters table view. Although, this action is only for Angularized clusters panel.
en_GB: Scale-in and Scale-out actions for cluster added. These actions are added as row action for each cluster in Clusters table view. Although, this action is only for Angularised clusters panel.

en: Switched to OSC module. Previously the client module for senlin API have been used from senlin command module. Now the senlin command module has retired and the client module for OpenStack Client is used to call senlin API.
en_GB: Switched to OSC module. Previously the client module for Senlin API have been used from Senlin command module. Now the Senlin command module has retired and the client module for OpenStack Client is used to call Senlin API.

en: The load-edit directive is used. The Spec field on Profile creation dialog and Policy creation dialog use load-edit directive newly added into Horizon.
en_GB: The load-edit directive is used. The Spec field on Profile creation dialogue and Policy creation dialogue use load-edit directive newly added into Horizon.

en: Update action for receiver is added. This action is added as row action for each receiver in Receivers table view. Although, this action is only for Angularized receivers panel.
en_GB: Update action for receiver is added. This action is added as row action for each receiver in Receivers table view. Although, this action is only for Angularised receivers panel.

en: [`blueprint add-cluster-resize-action <https://blueprints.launchpad.net/senlin-dashboard/+spec/add-cluster-resize-action>`_] Resize action for cluster is added. This action is added as row action for each cluster in Clusters table view. Although, this action is only for Angularized clusters panel.
en_GB: [`blueprint add-cluster-resize-action <https://blueprints.launchpad.net/senlin-dashboard/+spec/add-cluster-resize-action>`_] Resize action for cluster is added. This action is added as row action for each cluster in Clusters table view. Although, this action is only for Angularised clusters panel.

en: [`bug 1805740 <https://bugs.launchpad.net/senlin/+bug/1805740>`_] Fixed senlin dashboard to work with latest openstacksdk version.
en_GB: [`bug 1805740 <https://bugs.launchpad.net/senlin/+bug/1805740>`_] Fixed Senlin dashboard to work with latest openstacksdk version.

en: [`bug/1742599 <https://bugs.launchpad.net/senlin-dashboard/+bug/1742599>`_] Fixed issue the deleted item is selected again with batch delete. Items recently deleted with batch action had been shown in deletion confirmation dialog when execute the batch delete action again. And this had caused the conflict error due to trying to delete unexisting item.
en_GB: [`bug/1742599 <https://bugs.launchpad.net/senlin-dashboard/+bug/1742599>`_] Fixed issue where the deleted item is selected again with batch delete. Items recently deleted with batch action had been shown in deletion confirmation dialogue when execute the batch delete action again. This had caused the conflict error due to trying to delete a non-existent item.

en: [`bug/1754416 <https://bugs.launchpad.net/senlin-dashboard/+bug/1754416>`_] `region_name` was not passed on when using the senlin-dashboard. This makes the client always fallback on the first region. This issue was fixed.
en_GB: [`bug/1754416 <https://bugs.launchpad.net/senlin-dashboard/+bug/1754416>`_] `region_name` was not passed on when using the Senlin-Dashboard. This makes the client always fallback on the first region. This issue was fixed.
