+1 Don't deprecate, until the bass drops... lesson learned.
On Wed, Feb 15, 2012 at 11:22 PM, Soren Hansen <[email protected]> wrote: > 2012/2/14 Jesse Andrews <[email protected]>: > > The major lessons of keystone: > > Now that we're verbalising lessons learnt from Keystone, I'd like to add > another thing from back in the Diablo days: We should only ever depend > on code that already exists or is under our own release management. When > Keystone was very young, we deprecated Nova's built-in auth system, but > seeing as Keystone wasn't ready, nor was being tracked by our release > manager, we ended up releasing Nova with a deprecated auth system and a > preferred auth system that wasn't released yet. I'd like to avoid that > happening again. > > -- > Soren Hansen | http://linux2go.dk/ > Senior Software Engineer | http://www.cisco.com/ > Ubuntu Developer | http://www.ubuntu.com/ > OpenStack Developer | http://www.openstack.org/ > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
