On 20/07/2016 10:16, Rob Cresswell wrote: > Hey all, > > So we've had a few issues with plugin stability recently, and its > apparent that many plugins are building off Horizon master as a > dependency. I would really advise against this. A more manageable > development process may be to: > > - Base stable plugins against a stable release of Horizon > - Base WIP versions/new plugins off the last Horizon milestone, b2 in > this case, and then bump the version and capture issues within the same > patch. This should prevent random breakages, and should allow you to > just look at the release notes for that milestone.
So this would mean changing tox.ini or requirements files after each horizon release? This dovetails nicely with the other thread about how we should be doing cross project interactions. What would be best, would be having horizon released as a separate library on pypi like the clients and oslo libs. Then openstack-dashboard, and all the plugins could rely on the same base library, without hacks like: deps = -r{toxinidir}/requirements.txt -r{toxinidir}/test-requirements.txt http://tarballs.openstack.org/horizon/horizon-master.tar.gz in tox.ini or # Testing Requirements http://tarballs.openstack.org/horizon/horizon-master.tar.gz#egg=horizon in (test-)requirements.txt Is that on roadmap? > On the Horizon side, we've moved our FF a week earlier, so I think that > week combined with the usual RC period should be enough time to fix > bugs. We'll aim to make sure our release notes are complete with regards > to breaking issues for plugins, and deprecate appropriately. > > Rob __________________________________________________________________________ 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