7431 - Create logging tool to detect new preferences and preferences without default values

Status: RESOLVED WONTFIX

(Core :: Preferences: Backend, enhancement, P3)

Description

[Tina Ornduff]

Need to create a logging tool to generate a text file containing a list
of preferences that are new, do not have default values, or have not been
documented. If you generate the initial list, I will compare it to the current
list of documented preferences. Once I have determined the ones that are
missing, I will check it in to mozilla/modules/libpref/src/init as
"goodprefs.js." The text file generated by the logging tool will be given to QA
and when a new preference is generated, a bug will be assigned to the person
responsible.

Comment 1

[mcmullen]

Removing "platform = PC". Target is M8

Comment 2

[selmer (gone)]

Don, this isn't critical for M8, but the longer we go without the harder it gets
to correct.

Comment 3

[chris hofmann]

I think I might be able to help out on this one.
have a look at this lxr query and lets look at
how we could clean this up and refine it to get
the presentation cleaned up to something that makes
sense for anyone who might need to use it.
http://lxr.mozilla.org/seamonkey/search?string=pref%5C%28

once we figure out what we need we can get the grep hooked
to a cron job and start comparing time slices to look for new
pref change checkin's

Comment 4

[selmer (gone)]

Chris, one of the main things we neede was to map the change back to the person
who did the checkin.  Is it possible to add that to the report you're
generating?  Tina needs to be able to use this report and she's not generally
going to go in and read code or do CVS queries.

Another thing is that it would be good to prune out references to prefs that
have already been documented.  It's not clear how you could filter this output
for that, but maybe the problem goes away when you're only looking at a week's
worth of checkins.

Comment 5

[sairuh (rarely reading bugmail)]

spam: in my testing realm, so reassigning qa contact to me, en masse.

Comment 6

[leger]

Moving all libPref component bugs to new Preferences: Backend component.  
libPref component will be deleted.

Comment 7

[Gagan]

prefs to mcafee

Comment 8

[Gagan]

argh... didn't work the last time. pardon the spam. ->mcafee

Comment 9

[don]

Move to Future milestone.

Comment 10

[sairuh (rarely reading bugmail)]

this would be so nice, but alas...

Comment 11

[Chris McAfee]

backend prefs

Comment 12

[Daniel Veditz [:dveditz]]

wontfix

Comment 13

[Jason Bassford]

Based on the last comment, it looks like this was resolved incorrectly - since
Daniel made the comment and resolved it, it looks like a simple keyboard slip. 
(There is certainly no patch that's been checked in that's mentioned as the
opposite resolution.)

-> WONTFIX

Comment 14

[Daniel Veditz [:dveditz]]

Thanks for catching and fixing the resolution mistake