shrinking as an absolute value in the near term.
>
> Once again I am sorry for any confusion I may have caused.
>
> :chutten
>
>
> On Tue, Nov 1, 2016 at 11:08 PM, Peter Dolanjski
> wrote:
>
>> Chutten is not as categoric as you are:
>>>
>>>
16: -1.2%
Sure, there were larger drops in the summer that seemed to have eased off
in Sept./Oct. but it's too early to tell if that's just some weirdness from
seasonality.
Peter
On Tue, Nov 1, 2016 at 9:56 PM, Mike Hommey wrote:
> On Wed, Nov 02, 2016 at 09:28:40AM +0800, P
On 10/31/2016 3:54 PM, juar...@gmail.com wrote:
>
> Discontinuing support for 10% of users sounds like shrinking 10% of
> customers, lay off 10% of employees, reduce 10% of funds for investments.
I can tell you that the evidence we have does not support the notion that
end of life (or the approa
>
> What I think would be helpful if Mozilla does go with this plan, is that,
> first, Mozilla sets a definite end date up front for ESR 52 and, second,
> that Mozilla has puts out the message as to what and why this is happening.
> Setting an end date for support will give everyone a timeline to w
>
> On 10/25/2016 6:26 AM, Ehsan Akhgari wrote:
>
>> FWIW, and to the extent that my opinion matters on the topic, I strongly
>> disagree that breaking the websites that people use silently is the
>> right thing to do.
>>
>> Let's ignore the HTTPS Everywhere part of the thread, and instead pay
>> m
While this doesn't definitively answer your question, it may provide some
insight:
We ran a survey of Chrome XP users (N=819) after Chrome's end of life
message was shown in the product (English only). The results showed:
-
About half the sample plan to continue using Chrome on XP without
Thanks for taking the time to provide thorough feedback.
3) For Windows Vista, I don't see where the fire is. I realize that it has
> a vastly smaller user base, but it is close to Window 7 code base and API
> wise.
I'm sure the engineering team can probably provide a more detailed response
on t
on of feedback from this email, I will be
drafting a blog post describing the finalized plan. In addition, we'll be
using some form of in-product messaging to inform users.
If you have questions/comments, please reply to the *firefox-dev* mailing
list.
Thanks,
*Peter Dolanjsk
8 matches
Mail list logo
