Hi Jess, That's a good question. I'll provide a few lists here to try to explain.
Reasons: Chrome, Firefox, and Internet Explorer are pushing the latest versions to users Reduce time spent working around issue of older browsers Reduce time spent testing across a large sent of browsers Pros: Can work with latest supported technology less targeted work arounds (can also remove any that are in place) faster performance smaller code base can use more latest JS, CSS, and HTML features Reduce time spent on testing (we can drop 3 of the 7 platforms we tested with for Infusion 1.5) Cons: Infusion may not work in legacy browsers (although we'll take patches where appropriate). Most likely will be an issue for those locked down to an older version of IE, or for an IE user stuck on Windows XP I hope that helps Justin On Jun 17, 2014, at 12:51 PM, Jess Mitchell <jessmitch...@gmail.com> wrote: > Hey Justin, > > Thanks for putting this all out there. I’m curious about Proposal 1 — can you > say more about what the implications are, why you’re recommending this, and > break down what it means (pros and cons)? > > Thinking aloud basically… > > Jess > > > On Jun 17, 2014, at 12:48 PM, Justin Obara <obara.jus...@gmail.com> wrote: > >> We've made it through and tagged Infusion 1.5 today. The official >> announcement will follow after the documentation work has been completed. >> >> However, we are now open to start working on the next release (Infusion >> 2.0). The first two issues we should tackle are as follows. >> >> Updating the version number >> http://issues.fluidproject.org/browse/FLUID-5449 >> >> Moving the demos and tests to be siblings of src >> http://issues.fluidproject.org/browse/FLUID-5217 >> >> I'd also like to make the following two proposals related to testing and >> jira cleanup. >> >> Proposal 1: >> >> For Infusion 2.0 and beyond I propose we only test with the latest versions >> of Chrome, Firefox, Internet Explorer, and Safari. This will be a slight >> departure from the support we had for Infusion 1.5 where we supported IE 8, >> 9, 10 & 11. >> >> >> Proposal 2: >> >> After every release there is a lot of jira cleanup needed. I'd like to take >> the opportunity to close ("won't fix") all issues related to deprecated >> features, apis, and etc., as well as those that are specific to browsers we >> are no longer tracking. >> >> Please let me know ASAP, as we'd like to start in on the jira clean up right >> away. >> >> Thanks >> Justin >> _______________________________________________________ >> fluid-work mailing list - fluid-work@fluidproject.org >> To unsubscribe, change settings or access archives, >> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work >
_______________________________________________________ fluid-work mailing list - fluid-work@fluidproject.org To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
