Hello netstackers, The branch for the blueprint https://blueprints.launchpad.net/quantum/+spec/api-framework-essex is about to be proposed for merge. Before doing that, I'd like to ask the community whether it makes more sense to update the framework for core API and extensions in a single branch or divide this work into two branches (and possibly blueprints).
Reasons for changing everything in a single branch: - Core API and extension share a lot of code in the wsgi framework. If we go for separate branches we will end up with core API using the new "resource" abstraction, whereas extension API will still use the old "controller" abstraction. - For the same reason as above, updating the core and extension frameworks in while branch will result in a much cleaner and readable code base. Reasons for doing separating changes to core API and extensions: - Lack of integration testing for extension API (I don't know whether I'm right here, but I think we now have integration testing for core API only). This means changes into the extension framework might have unforeseen effects not caught by unit tests. - Smaller changesets make reviewers' task easier! I'm really quite undecided here, even though I'd slightly prefer the second option (separate branches). Any feedback? Salvatore
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
