I hacked up a crude script to collate the results from Gregory's
spreadsheet that collates the results across a subdirectory into sort of
useful results:
https://github.com/amccreight/gecko-components
From the spreadsheet, do "download as" and then "comma separate values" to
get the input format.
I was accidentally sorting based on bug component name, not the count of
bugs. The spreadsheet has been updated.
Sorry for the confusion.
On Wed, Mar 4, 2015 at 5:50 PM, Botond Ballo wrote:
> I see other wrongness in that spreadsheet, too. For example, for the
> first file I cared to check, gfx
I see other wrongness in that spreadsheet, too. For example, for the
first file I cared to check, gfx/layers/apz/src/APZCTreeManager.cpp,
the spreadsheet gives "Firefox for Metro :: General" as the bug.
However, I just checked, and out of the 80 bugs that touched the file
since its creation, which
L. David Baron:
> Having looked at the data for layout/, I think the results in the
> spreadsheet are mostly wrong, and I'd rather not populate things
> using it.
A lot of the wrongness is files which weren’t updated recently, except
for tree-wide changes such as introducing nullptr, which got fil
On Wednesday 2015-03-04 12:21 -0800, Martin Thomson wrote:
> On Tue, Mar 3, 2015 at 7:04 PM, Gregory Szorc wrote:
> > This spreadsheet contains a list of files and their most frequently
> > associated bug component from commits landed since 2014.
> >
>
> Is there any harm in automatically marking
On Tue, Mar 3, 2015 at 7:04 PM, Gregory Szorc wrote:
> This spreadsheet contains a list of files and their most frequently
> associated bug component from commits landed since 2014.
>
Is there any harm in automatically marking files based on this then having
the community review and fix later?
Some quick updates.
https://gecko.readthedocs.org/en/latest/build/buildsystem/mozbuild-symbols.html#mozbuild-subcontext-files
now contains the full documentation on the "Files" type. These docs were
truncated before. Included is differences between '*' and '**'.
I have plans to stand up a web ser
This spreadsheet contains a list of files and their most frequently
associated bug component from commits landed since 2014.
https://docs.google.com/spreadsheets/d/1cz2-UC_LN_OFM2q67rKi6Mo-2TpdN8fTiH8LstZJ4PM/edit?usp=sharing
If a file is missing, it likely hasn't been modified in the past ~14 mo
Is there any kind of existing code around that would look at the bugs for
the commits for the files in a directory and create some kind of count of
the components they were filed in? dom/ has something like 90
subdirectories, and it would be nice to be able to quickly get some kind of
census like
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 use
10 matches
Mail list logo
