On 2026-03-12 08:04:20 +0100 (+0100), Michał Nasiadka wrote:
Looking at https://codesearch.opendev.org/?q=import%20horizon&i=nope&literal=nope&files=&excludeFiles=&repos= horizon is used more like a library in the respective UI plugin repositories [...]
Neutron had a similar problem, and split out a neutron-lib deliverable to deal with it. The constraints list covers neutron-lib which gets its final release of the cycle at the same time as other libraries, and does not constrain neutron itself which is released with other services at the end of the development cycle. I worry that in this case the Horizon team probably lacks sufficient bandwidth to undertake such a split (doing it took the Neutron team years and they were a larger team to begin with), so we may need to look at alternative compromises like treating the horizon deliverable as a library in release management in order to be consistent with how it's handled in requirements, or changing the way horizon is installed when testing plugins. -- Jeremy Stanley