On 25/04/2018 18:40, Jeremy Stanley wrote:
This came up again a few days ago for sahara-dashboard. We talked through some obvious alternatives to keep its master branch from depending on an unreleased state of horizon and the situation today is that plugin developers have been relying on developing their releases in parallel with the services. Not merging an entire development cycle's worth of work until release day (whether that's by way of a feature branch or by just continually rebasing and stacking in Gerrit) would be a very painful workflow for them, and having to wait a full release cycle before they could start integrating support for new features in the service would be equally unfortunate.
+1
As for merging the plugin and service repositories, they tend to be developed by completely disparate teams so that could require a fair amount of political work to solve. Extracting the plugin interface into a separate library which releases more frequently than the service does indeed sound like the sanest option, but will also probably take quite a while for some teams to achieve (I gather neutron-lib is getting there, but I haven't heard about any work toward that end in Horizon yet).
+1 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
