On 10/24/15 1:41 AM, Bobby Holley wrote: > We have three options: > (1) Build peers do a bunch of extra work to support c-c in a separate repo. > (2) We land c-c in m-c, so that build peers can support it without much > extra work. > (3) We don't land c-c in m-c, build peers ignore c-c, and TB fends for > itself as pure downstream. > > (1) seems strictly sub-optimal. The decision here is pretty much between > (2) and (3).
I think there is another option here. Although I would of course prefer (2), I think we could add: (4) We land c-c in m-c, build peers ignore comm projects, TB folks help with any build issues that break comm projects. Philipp _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
