I know of at least 2 different companies who have out-of-tree Quantum extensions/plugins. Module import locations are a defacto API and we need to make sure that we're not inflicting too much pain for folks who have current implementations. We currently don't mark certain code APIs as stable, but might to need to consider it going forward. This will become more important when building a larger Quantum software ecosystem.
mark On Nov 5, 2012, at 3:57 PM, Salvatore Orlando <[email protected]> wrote: > Hi Mark, > > I did look at that change (not all the files, but it seems that they're just > changing import paths). > The change looks pretty innocuous to me; can you elaborate a bit more on what > you intended with allowing out of tree extensions? > > Salvatore > > On 5 November 2012 19:00, Mark McClain <[email protected]> wrote: > I wanted to make sure that all of the cores saw this proposed change: > > https://review.openstack.org/#/c/15425/ > > Should we have a deprecation period during Grizzly to allow out of tree > extensions and plugins to catch up with the change? > > mark > > > -- > Mailing list: https://launchpad.net/~quantum-core > Post to : [email protected] > Unsubscribe : https://launchpad.net/~quantum-core > More help : https://help.launchpad.net/ListHelp >
-- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
