(forth attempt at posting this -- for some reason it seems like it keeps getting blocked...)
-------- Original Message -------- From: - Fri Sep 09 13:44:26 2011 X-Identity-Key: id12Message-ID: <4E6A69BF.4070601＠tlinx｡org>Date: Fri, 09 Sep 2011 12:32:15 -0700From: Linda A. Walsh <firebug＠tlinx｡org>X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666MIME-Version: 1.0Subject: Fwd: [firebug] Re: Firebug 1.8.2Content-Type: text/html; charset=UTF-8Content-Transfer-Encoding: 7bit alfonsoml wrote: > So you don't have the time to upgrade your browser, and instead you > want that other people devote their time to support the version that > you've chosen to stay with? > --- Just because 30% of the people haven't upgraded... not just me... Are you trying to make me feel like I'm somehow all alone in not upgrading just yet? > Just for how long should they stay supporting it? > ---- It depends, but usually when the user base gets down below some fractional value like 1/3, 1/4, 1/5... depends on the product and how it is used. Also depends on how well the old product works or if it crashes or has features that just are broken. > And when you finally decide to upgrade, I think that you'll expect a > fully supported and polished version of Firebug that doesn't have any > problem with the current version of Firefox. ---- I don't have that now, so why would I expect it when I upgrade? Usually I expect a downgrade in quality when I upgrade. Developers tend to focus on new features and new stuff, while not devoting enough time to maintenance or fixing of problems -- in general, I dread upgrades because of the focus on new features, that usually bring a host of new bugs (this is 'in general' not specific to firebug). It's rare that a new release brings an upgrade in quality without some increase in new features that also bring New bugs (security patches usually excluded from that count, though not always). > I instead would rather see a shift to support even Aurora, as that's > the version that will be released in 3 months and it's better to find > bugs as soon as possible to fix regressions in Firefox. > ---- It is very troublesome for you to indicate how incompatible Aurora is with previous versions. That's the problem all extension developers are facing right now. FF is a fast moving target with such widely incompatible features sets that extension developers find it impossible to support browsers released only yesturday!!! (3.6.22 was released yesterday, not in 2008, get with the program!)... I'm not asking for support for 3.6.0 -- just currently used browsers by more than 20% of the people, (arbitrary)... But 3.6.x was cut off with it's last update back when it till had over a 50% market share!... (June). That was it's last bug fix. Not asking for new features, but you focused, in your last few announcements about how many bugs you fixed. I'm not asking for full new version support in the prior versions -- just the bug fixes that you've been focusing on of late, as I often get hangs and panels that don't function well or at all in some cases, yet they claim no incompatibility. So let me rephrase my request/statement to be specific about bug-fixes, not about feature additions. That way you can focus on new features for the new browsers, but keep bug fixes maintained for the currently top 75-80% of the user base. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To view this discussion on the web visit https://groups.google.com/d/msg/firebug/-/vVn3x7bncpMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
