Hi all, I would like to bring to your attention some items for Quantum I think we should discuss during today's meeting.
* API specification I'm still keen on locking down the specification; by "locking down" I don't mean that we should freeze and any attempt to propose even the slightest change will unleash my wrath :). I simply want to make sure that after Diablo-4 we will not have anymore: o Backward-incompatible changes (I wish we will never have those) o Changes in the semantics of attributes In a nutshell, I would like to avoid changing the API in a way that then forces us to uodate our clients as well; If then there should be some API behaviour which we wish to change, I'm completely happy with it as long as it does not affects clients. * Unit tests for client tools Tyler has developed a thorough unit test suite for the client library. We will probably also need unit tests for client applications (cli and batch configuration at the moment); a good suite of unit tests will allow us to discover immediately if a change in API will cause one of these clients to break. * Diablo-4 release plan It is my opinion that D-4 should include also the authentication/authorization blueprint: https://blueprints.launchpad.net/quantum/+spec/quantum-api-auth And the api-alignment bug: https://bugs.launchpad.net/quantum/+bug/813433
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
