On Fri, Nov 6, 2015 at 1:46 PM, Mike Hommey <m...@glandium.org> wrote:
> On Fri, Nov 06, 2015 at 01:12:30PM -0600, Joshua Cranmer ? wrote: > > On 11/6/2015 12:38 PM, Doug Turner wrote: > > >I would have rather done this in a private email, but some replied and > said I wasn’t clear. > > > > > > > > >-> Do not merge comm-central into mozilla-central <- > > > > > > > > >1) I think merging comm-central is a bad idea as it will basically tax > all gecko + firefox developers forever. > > > > > >2) It isn’t clear that Thunderbird is a supported product anymore. > MoCo certainly isn’t responsible for it. I don’t think MoFo does anything > for it. > > > > I know that Thunderbird has been in talks with the Mozilla Foundation > about > > being officially supported by them, and I believe the only thing left is > to > > sign the ink on some papers for that. There are others who were involved > in > > those talks who could give more specific details. > > > > >3) We’re spending $ and time in Release on this project. I would > rather not have to do that given (2). > > > > > >4) This sets a bad precedent. I don’t think we want every application > built on top of gecko to be in mozilla-central. > > > > I've explained why this isn't really a precedent several times. > > > > > > > > >We don’t have all of the time and resources in the world. We have to > be very deliberate about what we work on. And Thunderbird — as it is now — > isn’t something MoCo is focusing on. Because of this, I really doubt > anyone in moco Release is going to futz with it. > > > > Except the release engineers in moco are already spending a good deal of > > time on managing the Thunderbird release engineering--exactly as Mozilla > > promised they would back in 2012. > > And other moco engineers are wasting time because of the status quo (and > I won't detail here because that's been covered in the thread already). > > Whether it happens in mozilla-central or somewhere else, this merge > *will* have to happen at some point. What about creating a "project branch" repository for comm-central that has the same root commit as mozilla-central? (This was discussed earlier in the thread.) We periodically merge mozilla-central into this repo but never the other way, thus isolating mozilla-central from comms foo. This does impact the ability to bisect projects independently. But it does enable code migration to occur easier since cherry picks and merges are easy. It also theoretically allows anyone to create and test commits on a "unified" repo. If/when we do get the green light to merge comm-central, it should just be a merge commit into mozilla-central. I think this gets us to a better position without fully exposing people who don't care about comm-central. This transition could occur whenever: it's up to the comm-central folks to green light it and make the infrastructure changes to support it. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
