Closed Bug 7431 Opened 25 years ago Closed 20 years ago

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

Categories

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

enhancement

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: ornduff, Assigned: dveditz)

References

Details

(Keywords: helpwanted)

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.
Removing "platform = PC". Target is M8
Status: NEW → ASSIGNED
Hardware: PC → All
Target Milestone: M8
Assignee: mcmullen → don
Status: ASSIGNED → NEW
Don, this isn't critical for M8, but the longer we go without the harder it gets to correct.
Target Milestone: M8 → M9
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
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.
Assignee: don → dp
Summary: Create logging tool to detect new preferences and preferences without default values → [RFE] Create logging tool to detect new preferences and preferences without default values
Target Milestone: M9
Assignee: dp → neeti
Status: NEW → ASSIGNED
Target Milestone: M11
Blocks: 11408
Target Milestone: M11 → M12
Target Milestone: M12 → M13
Target Milestone: M13 → M14
QA Contact: paulmac → sairuh
spam: in my testing realm, so reassigning qa contact to me, en masse.
Target Milestone: M14 → M15
Moving all libPref component bugs to new Preferences: Backend component. libPref component will be deleted.
Component: libPref → Preferences: Backend
Target Milestone: M15 → M16
Target Milestone: M16 → M20
prefs to mcafee
Status: ASSIGNED → NEW
Target Milestone: M20 → ---
argh... didn't work the last time. pardon the spam. ->mcafee
Assignee: neeti → mcafee
Component: Preferences: Backend → Preferences
Move to Future milestone.
Target Milestone: --- → Future
this would be so nice, but alas...
Keywords: helpwanted
Component: Preferences → Preferences: Backend
backend prefs
Assignee: mcafee → dveditz
Status: NEW → ASSIGNED
Summary: [RFE] Create logging tool to detect new preferences and preferences without default values → Create logging tool to detect new preferences and preferences without default values
wontfix
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
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
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WONTFIX
Thanks for catching and fixing the resolution mistake
You need to log in before you can comment on or make changes to this bug.