Difference between revisions of "Meetings/Horizon"
< Meetings
(→Agenda for Next Meeting) |
(→Agenda for Next Meeting) |
||
| Line 9: | Line 9: | ||
* Notices | * Notices | ||
* Action items from the previous meeting | * Action items from the previous meeting | ||
| + | ** 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 | ||
* Open Discussion | * Open Discussion | ||
** Don't we discuss horizon release and versioning model any more? I see the topic was dropped from the meeting agenda... I don't want to add it for every meeting. (amotoki) | ** Don't we discuss horizon release and versioning model any more? I see the topic was dropped from the meeting agenda... I don't want to add it for every meeting. (amotoki) | ||
Revision as of 14:06, 2 May 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
- 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.
- horizon release model: cycle-with-milestone vs cycle-with-intermediary
- Open Discussion
- Don't we discuss horizon release and versioning model any more? I see the topic was dropped from the meeting agenda... I don't want to add it for every meeting. (amotoki)
