Support for the previously announced [1] intention to use moz.build to define metadata for files has now landed on mozilla-central with the landing of bug 1132771 [2].
This is important to you because there are plans to leverage this metadata to make it easier to get stuff done. Some potential uses include: * automatically filing bugs against the proper component * automatically selecting reviewers for a patch * intelligently scheduling automation jobs based on what changed *But we can't do any of these things unless there is data to drive it.* That's where you come in. I would kindly request that you take a few minutes to help define which files in mozilla-central map to which Bugzilla components. The process for doing this is relatively simple: 1) Read the docs on how file metadata works [3] 2) Write and land a patch (see [4] for an example patch) The newly-landed `mach file-info` command can be used to help you query metadata on files. Run `mach help file-info` for usage. If you need help, ask in #build. If you don't like how things work or if you have a suggestion for improvement, file a new bug depending on bug 1132771 and we'll go from there. You may be interested in bugs already on file, which include support for defining code reviewers (bug 1137042) and the ability to audit metadata for correctness (bug 1137043). Adding or changing "Files" entries in moz.build files does not require build peer review. [1] https://groups.google.com/d/msg/mozilla.dev.platform/iXr70VgapWk/GkTCcKRjNi8J [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1132771 [3] https://ci.mozilla.org/job/mozilla-central-docs/Tree_Documentation/build/buildsystem/files-metadata.html [4] https://hg.mozilla.org/integration/mozilla-inbound/rev/4cc39c54099d _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
