Difference between revisions of "Meetings/Horizon"
< Meetings
(→Agenda for Next Meeting) |
(→Agenda for Next Meeting) |
||
| Line 20: | Line 20: | ||
*** However, the versioning might be surprising for horizon consumers like operators/users. | *** However, the versioning might be surprising for horizon consumers like operators/users. | ||
** horizon-lib again might be a good candidate on this problem. | ** horizon-lib again might be a good candidate on this problem. | ||
| + | *** http://lists.openstack.org/pipermail/openstack-dev/2018-June/131458.html | ||
** [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128310.html | ** [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128310.html | ||
* Improve Horizon Testing | * Improve Horizon Testing | ||
Revision as of 15:03, 27 June 2018
The OpenStack Horizon Team holds public meetings in #openstack-meeting-alt, weekly on Wednesdays at 1500 UTC.
See http://eavesdrop.openstack.org/#Horizon_Team_Meeting for recordings of previous meetings and the upcoming meeting schedule.
Everyone is encouraged to attend!
Agenda for Next Meeting
- Notices
- Action items from the previous meeting
- Community Goals
- mox => mock migration
- Current status: https://etherpad.openstack.org/p/horizon-unittest-mock-migration
- horizon release model: cycle-with-milestone vs cycle-with-intermediary
- The infra change (zuulv3 configuration change) [1] now forces horizon plugin developers to handle horizon dependencies in a tricky way.
- The OpenStack CI installs horizon master (based on tox-siblings) and it works well, but local testing will fail because it installs horizon queens.
- This problem is based on a horizon version published to PyPI.
- horizon is a kind of library from perspective of horizon plugins. from this point, it is reasonable to publish horizon with cycle-with-intermediary.
- If so, the version of horizon would follow semantic versioning. It would help horizon plugin developers.
- However, the versioning might be surprising for horizon consumers like operators/users.
- horizon-lib again might be a good candidate on this problem.
- [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128310.html
- The infra change (zuulv3 configuration change) [1] now forces horizon plugin developers to handle horizon dependencies in a tricky way.
- Improve Horizon Testing
- Blueprint https://blueprints.launchpad.net/horizon/+spec/improve-horizon-testing
- Getting rid of Nose test runner
- Open patches:
- Cross-project CI jobs to test plugins
- Django 2 support
- Horizon feature gap
- Review priority
- https://etherpad.openstack.org/p/horizon-reviews-priority
- Feel free to add your patches to the etherpad above
- Open Discussion
