Rick Alther schrieb:
> On 10/5/2011 16:59, Robert Strong wrote:
>> The pref app.update.never.X.Y just prevents prompting the user and it
>> doesn't prevent manual updates. If you don't want users to be able to
>> update to the updates advertised by Mozilla you need to disable updates
>> by locking the app.update.enabled with a value of false and to control
>> which updates are deployed you have to deploy updates yourself. For the
>> ESR under proposal the current thought is to provide a new update
>> channel that would only get the ESR releases but that is still under
>> discussion.
>>
>> Robert
> Thanks Robert. Not what I was hoping for. We allow our users to do
> manual updates (and accept security point updates). The
> app.update.never.X.Y works great as they don't see 3.6 -> X updates,
> only the 3.6 updates. However, advertised updates ignore this pref.
>
> What I was hoping for was a way to major version updates, including
> advertised updates, yet allow security updates to the existing level to
> proceed unimpeded. It appears I can't have both.
I think you are misunderstanding our phrasing here. "Advertised update"
means that we prompt the user for update to a new "major" version, which
is exactly what you say that app.update.never.* successfully prevents,
from how I read your message.
What kind of update do you mean that ignores it?
Robert Kaiser
--
Note that any statements of mine - no matter how passionate - are never
meant to be offensive but very often as food for thought or possible
arguments that we as a community should think about. And most of the
time, I even appreciate irony and fun! :)