Currently, there are 3 bug components related to the build system in mozilla-central:
Core :: Build Config Firefox :: Build Config Toolkit :: Build Config (The latter 2 aren't really used that often.) There are also a handful of other pieces of software that have strong tie-ins to the build system. These include: * Core :: mach * system bootstrap support * Various mach commands like "mercurial-setup" and "doctor" * mozharness, buildbot, and TaskCluster automation (The middle 2 don't really have bug components.) Maybe it's just me, but I've been finding Core :: Build Config a bit overwhelming, especially when I want to e.g. find all bugs impacting a sub-component of the build system, like artifact builds. I can't help but feel important bugs are getting lost in the noise of the monolithic Core :: Build Config component and others get lost in components nobody pays attention to. I'd like to float the idea of restructuring the build system's bug components. How it would look, I'm not sure. I'll throw out the idea for a top-level Bugzilla Product for all things related to the build system. e.g. Build System :: bootstrap and system configuration Build System :: moz.build, configure, and build definitions Build System :: artifact builds Build System :: toolchains and platform integration Build System :: automation jobs and tasks (Obviously this list isn't final and bikeshedding would be necessary.) I know we've had this conversation in the past. I agree there are merits to a single bucket for everything. Part of this email is me following the philosophy that you should always re-evaluate past decisions and see if they are still justified. So, are there any changes since last time we considered this that would warrant a Bugzilla restructure?
_______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
