It generates lists of fixed bugs related to Firefox for desktop in Mozilla Mercurial pushlogs
当前为
This userscript applies to Mozilla Mercurial pushlog pages.
It generates a list of only the bugs related to Firefox for desktop in Mozilla Mercurial pushlogs. It's basically for creating lists similar to the "The Official Win32 xxxxxxx builds" in Firefox Builds • mozillaZine Forums but for any date interval.
Example links where the script applies to: (changelogs for the last 1 day interval in these examples) Nightly: https://hg.mozilla.org/mozilla-central/pushloghtml?startdate=1+day+ago&enddate=now Inbound: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?startdate=1+day+ago&enddate=now fx-team: https://hg.mozilla.org/integration/fx-team/pushloghtml?startdate=1+day+ago&enddate=now Aurora: https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?startdate=1+day+ago&enddate=now Beta: https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?startdate=1+day+ago&enddate=now
Also, (about the "enddate" value when you do such a search):
instead of putting "now" you may put the changeset of your currently installed build (via about:buildconfig|click on that link)
so that you may view only the bugs that have been fixed till your current build - not those that have been fixed til the current time in the relevant branch.
For example: (for inbound) instead of using:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?startdate=1+day+ago&enddate=now
you may enter this: (it's for the changeset of this build)
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?startdate=1+day+ago&enddate=c4dd82aa903d
Screenshots of the resulting list:
v5
v4
and screenshot of progress logging in Web Console:
During the procedure, you may open the Web Console (Ctrl+Shift+K) to monitor progress.
Notes:
In the (current) v5 it displays the results as a sortable table (instead of a plain list),
showing in an extra column the "Last Modified Date" of each bug, the values of which are converted to relative time (e.g, "1 hour ago") taking account the user's timezone. (I've created a custom sorter for this extra column).
By default it's sorted by "Modified Date" and "Product:Component" - as a mozilla-inbound user I find this most practical because this way I can check whether any notable bugs have been just fixed, and therefore if it's worth downloading the latest m-i build.
But, you may sort the table as you wish: you can sort multiple columns simultaneously by holding down the Shift key and clicking a 2nd, 3rd or even 4th column header.
You may also comment out line #317 and uncomment #316 in order the results to be sorted by "Product:Component" (and then by "Summary") only, by default.
In v5.2 I added separators between groups of the same timestamps (screenshot) (comment out lines 319-328 to disable this)
The procedure:
title, status, product. component, platform, whiteboard and last_change_time values.Product: Component stringdialog.
(for the "Modified Date" column, the following libraries are used: tablesorter, moment.js, moment-timezone.js, jsTimezoneDetect and date.js)
What it considered relevant/irrelevant:
(info provided kindly by winapp2 and Josa, both maintainers (the first no longer) of the "Official Win32 build" threads)
Relevant Status values
Relevant Product values
Relevant Component value (belonging to Product: Core)
Irrelevant Component values (all belonging to Product: Core)
Irrelevant are also considered bugs with restricted access (you may find the bugs which were filtered out for being private, by opening Web Console and enter 'requires authorization' in the 'Filter output' textbox. Then you may click on the relevant links to open them (those that you have access to).
Thanks a lot to: