The argument that I was going to make in support of separate projects: The separation of projects should lead to separation of concerns and better APIs. But that requires a stable API first and we won't be there for a while. The other arguments I had have been resolved or overcome by the discussion here. So, while I was in favor of this originally, now is not the time for splitting (if ever).
Francis On Thu, Dec 12, 2013 at 4:27 AM, Evan Dandrea <[email protected]> wrote: > On 12 December 2013 05:32, Andy Doan <[email protected]> wrote: >> I think that's a bit of silo thinking. eg, We all need to care about what's >> going into the image-builder and at least be cognizant of the fact that >> there are changes going into it. > > +1 > > It also means less work for the single command deployment and CI of CI. > > -- > Mailing list: https://launchpad.net/~canonical-ci-engineering > Post to : [email protected] > Unsubscribe : https://launchpad.net/~canonical-ci-engineering > More help : https://help.launchpad.net/ListHelp -- Francis Ginther Canonical - Ubuntu Engineering - Continuous Integration Team -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
