Post Infusion 1.5 proposal

[Justin Obara]

Hi Jan,

The mobile browsers we have listed there are definitely out of date, I left a note that they are not currently being followed. I was debating removing the section, but left it here for history. Perhaps it would be less confusing if it were just gone.

Thanks
Justin

On Jun 26, 2014, at 12:06 PM, Richards, Jan <jrichards at ocadu.ca> wrote:

> Hi Justin,
> 
> I think the Android version supported should be more recent that 2.2...it has just 0.8% of Android installations at this point (https://developer.android.com/about/dashboards/index.html).
> 
> Cheers,
> Jan
> 
> 
> (MR) JAN RICHARDS
> PROJECT MANAGER
> INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
> OCAD UNIVERSITY
> 
> T 416 977 6000 x3957
> F 416 977 9844
> E jrichards at ocadu.ca
> 
> ________________________________________
> From: fluid-work-bounces at fluidproject.org [fluid-work-bounces at fluidproject.org] on behalf of Justin Obara [obara.justin at gmail.com]
> Sent: June-26-14 12:01 PM
> To: Fluid-Work Mailing List Work
> Subject: Re: Post Infusion 1.5 proposal
> 
> I've updated the browser support to be latest Chrome, Firefox, Internet Explorer and Safari.
> 
> http://wiki.fluidproject.org/display/docs/Browser+Support
> 
> Thanks
> Justin
> 
> On Jun 22, 2014, at 8:07 AM, Colin Clark <colinbdclark at gmail.com> wrote:
> 
>> Hi Justin,
>> 
>> On Jun 17, 2014, at 7:48 PM, Justin Obara <obara.justin at gmail.com> wrote:
>> 
>>> 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.
>> 
>> We've discussed browser support for Infusion 2.0+ quite extensively in the past, and this proposal is entirely consistent with these discussions.
>> 
>> +1 for supporting only the latest versions of Chrome, Firefox, Safari, and IE.
>> 
>>> 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.
>> 
>> +1. Tidying JIRA up based on the above policy makes sense to me.
>> 
>> Colin
> 
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work