services.sync.log.appender.debugLog.enabled should be on for nightlies. If we are concerned about disk IO, we can turn it off for every beta and release. I think by default testers should have access to that data to better track down transient issues.
The lack of debug logs by default in nightlies has an unexpected impact on Services Ops. Each time something breaks in the client, folks ask us "Is production down?". Most of the time, that isn't the issue, and we have to somehow reproduce their problem. This is especially problematic with transient wifi issues and upgrade issues. Therefore I'm raising this to CRITICAL; every day we wait to push this into nightlies, we lose valuable information that might help us find and/or fix potential sync blocker bugs.
Severity: normal → critical
Pushing it over to mconnor, feel free to reassign.
Assignee: nobody → mconnor
mconnor is unavailable for 2 weeks, who else can review this?
I don't think we want to temporarily flip the pref and then flip it back before each release because that way lies madness. There are ways to programmatically determine whether we're on a release build or not a. inspect the "app.update.channel" pref  b. ifdef MOZ_OFFICIAL_BRANDING  Option a. would probably be best applied in Service._initLogs(), option b. could be applied as a preprocessor rule in services-sync.js. Thoughts? Preferences?  https://mxr.mozilla.org/mozilla-central/source/toolkit/content/debug.js#70  https://mxr.mozilla.org/mozilla-central/source/toolkit/components/search/nsSearchService.js#151
OS: Mac OS X → All
Hardware: x86 → All
I'd prefer b, as there has been some discussion about possibly changing the channel names in the future.
Guessing this wasn't actually critical, though I agree that it would still be nice to have...
Severity: critical → normal
You need to log in before you can comment on or make changes to this bug.