Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.apps.firefox
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion User-configurable preference removal/deprecation policy
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Rob Campbell  
View profile  
 More options May 9 2011, 11:23 am
Newsgroups: mozilla.dev.apps.firefox
From: Rob Campbell <rcampb...@mozilla.com>
Date: Mon, 9 May 2011 12:23:56 -0300
Local: Mon, May 9 2011 11:23 am
Subject: Re: User-configurable preference removal/deprecation policy
Print | View thread | Show original | Report this message | Find messages by this author

On 2011-05-09, at 11:50, Johnathan Nightingale wrote:

> On 2011-05-09, at 10:38 AM, Panagiotis Astithas wrote:

>> I wanted to ask about our standard policy regarding the removal or
>> deprecation of user-configurable preferences. The reason I'm asking is
>> because of bug 644419[1], where I want to remove the devtools.hud.loglimit
>> preference, that "appeared" in Firefox 4, for controlling the number of
>> displayed messages in the console. In fact "appeared" is probably not the
>> right word, since it is not visible in about:config by default, and not
>> documented anywhere AFAICT, apart from the source code. Our (the devtools
>> team) plan is to replace it with four separate knobs, one for each logging
>> category.

>> The question is, can we just kill it, or should we provide a deprecation
>> period, where both the old and the new knobs are available? Should that
>> period extend to infinity? The problem with deprecation in this case is that
>> there are some thorny issues regarding the combined behavior of these knobs
>> (who takes precedence, etc.), so a simple removal seems to make sense, if
>> possible.

> Based on the above, my personal take is that we kill it with fire. Would be interested to know how universally held that belief is, but if we can't kill an undocumented, invisible, expensive to maintain pref then what can we ever kill?

That was my gut-feeling as well.

I think +2 should be enough for this? :)

~ rob


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google