----- Original Message ----- > From: "Gregory Szorc" <[email protected]> > > The severity of the problem depends on who you are. By some accounts, > the build system is staying afloat. We are fixing major issues > (especially if they impact automation). And, people are still scratching > itches here and there. People are still able to build Firefox. So, the > problem is easy to glance over. But, some people have expressed > complaints directly to me. Who knows how many more are silently > resenting the current status.
This part always seemed quite strange to me - build config essentially has two consumers: developers and automation. While improvements to the core build system can benefit both, organizationally we only have a team of people dedicated to the automation side of things. Essentially this means we only make significant progress in the dev side when there's free time, or when frustration with the current state of the build system boils over and someone decides to put their real work aside for a while. This makes long term progress much harder to achieve. IMO there's no reason we can't deliver a 100% reliable, 0%-clobber, near-instantaneous turnaround build system experience to developers. We just love machines more, I guess. -Mike _______________________________________________ dev-builds mailing list [email protected] https://lists.mozilla.org/listinfo/dev-builds
