On Mon, Feb 29, 2016 at 08:21:18AM +0100, Andreas Jaeger wrote: > > Yes, they will officially become a part of Fuel project. First such > > example is likely to be the Murano plugin [0], so we can use it a the > > guinea pig to try out this process. > > > > [0] https://review.openstack.org/269567 > > > > As described in the corresponding spec [1], we plan this plugin to > > co-exist with the current non-plugin implementation for Mitaka, and then > > let the legacy non-plugin implementation be superceded by > > fuel-plugin-murano as soon as the latter reaches maturity (hopefully > > early in Newton cycle). > > > > [1] https://review.openstack.org/275124 > > Why is the corresponding spec not mentioned as part of the infra change?
We updated the change to reference the blueprint which in turn links to this spec. > > Since this is not a straight-forward moving of existing code into its > > own git repo (like we've recently done for fuel-virtualbox and fuel-ui), > > I think it's too early to register the new plugin repo in > > openstack/governance, but eventually (as soon as it's ready to become > > the default way to deploy Murano with Fuel) we should add it there. > > That's not a reason under the big tent to not add it to the governance > documentation. There's no need to incubate it outside the tree. Fair enough. I've posted a governance change and linked it to the infra change: https://review.openstack.org/286310 -- Dmitry Borodaenko __________________________________________________________________________ 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
