It seems to me this is a call for a census. Indeed as Vincent points out,
Enterprise can't upgrade really anything overnight... but we must beware
of user relationships which are not mutually beneficial.
If (for example) there is only one user who requires IE8 support and it
costs an additional 30 man/hours per month to continue support, IMO the
one user who requires it owes that time to the project.
I'm going to abstain from voting until I know:
#1 how many users need this (best if we can value the users in terms of
how much they contribute to the project, either directly or through
support contracts with developers who contribute).
#2 how many man/hours per month will be required in order to keep up IE8
support.
Does this seem logical?
Caleb
On 03/11/2014 03:12 PM, Ecaterina Moraru (Valica) wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for IE9,
so we should also adjust our support strategy by supporting newer browsers
(IE10, IE11) and dropping the support for old ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar the
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query support.
IE8 doesn't has support for media query natively, we would need Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1]
http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2]
https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs