On 23/10/15 04:43 AM, Gregory Szorc wrote:
- It adds burden to developers, needing to support those projects merged from comm-central. Just look around in mozilla-central at all the optional things that are not visible on treeherder and break regularly. The situation wouldn't be different in that sense. But the people that do care about those projects will have a better experience supporting them.The other serious concern is impact to automation. Are we going to close trees for Thunderbird failures? Are we going to run Thunderbird jobs on every push? (Do we do this now?)
This is a decision we can make independently of merging comm-central to mozilla-central. We have a lot of code living in mozilla-central that does not get tested per push, nor does it close the trees when it fails. Moving to m-c does not mean that the current state of affairs for thunderbird needs to change. Whether or not we'd like the current state of affairs for thunderbird to change is another matter, but it doesn't need to be a blocking issue w.r.t the merge.
Big +1 for the proposal btw. _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
