If there is anything broken in Essex due to this code, please let me know and we will take a look/fix it.
The main reason why we would like to have it in place - to make developers aware that there is somebody relying on particular functionality and/or particular function/module. Otherwise we will be in a constant merge conflict and every time we will need to manually review almost any change that is applied to the trunk and check if it anyhow affects/breaks it. Thanks, -Vladimir -----Original Message----- From: Kevin L. Mitchell [mailto:kevin.mitch...@rackspace.com] Sent: Thursday, March 15, 2012 9:53 AM To: Vladimir Popovski Cc: Vishvananda Ishaya; openstack@lists.launchpad.net Subject: Re: [Openstack] Removal of VSA Code On Thu, 2012-03-15 at 09:02 -0700, Vladimir Popovski wrote: > I was not aware of any issue with VSA code in diablo/stable (or at > least major issues). I'll point out that the code we're concerned about is the code in trunk, not the code in diablo/stable. There have been substantial changes to the code since diablo was released, which has resulted in bitrot in the VSA code and the attendant breakages to which Vish is referring. -- Kevin L. Mitchell <kevin.mitch...@rackspace.com> _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
