[sakai-core-team] Documentation - double check browser language

[Matthew Jones]

Yeah right, even in a lab situation they do eventually have plans to have
plans at least yearly to upgrade the lab as local software is going to also
have security issues. Most schools do that right before the semester
starts, so they should have the newest versions of all the software in
August (For US schools) which coincides with the Sakai upgrade.

It's generally going to be as easy for most places to upgrade their labs as
it is to get a patch created, fixed and applied in their server. And the
reality of partial support browsers is that unless the jira has a patch
attached it just won't get fixed and eventually just closed as Won't Fix,
since it's not worth the time to downgrade browsers figure out the problem.
(especially when it's often bug in the browser)

Anyway, I think this section is finally getting less important since
Microsoft no longer supports Windows XP/IE 8 anymore. That really was the
browser that caused most of the backward compatibility problems.


On Mon, Jun 16, 2014 at 8:31 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

> Except for lab configurations which I hear about sometimes in some
> institutions, in which it may be beyond the influence of a Sakai
> administrator to get the browsers upgraded. The labs are locked down tight
> by central IT or a departmental IT.  I'm not sure how pervasive this
> problem is.
>
> It would seem like it would be more work for IT administrators to support
> old software that becomes less compatible over time and with more security
> holes?
>
> -- Neal
>
>
>   Matthew Jones <matthew at longsight.com>
>  June 16, 2014 at 8:26 AM
> Yeah, I bump the "file any bugs line"  up to be under supported, and even
> bump the "We encourage you to upgrade" line up to partial support.
>
> There's really no reason anyone should be running a browser old than the
> ones we are supporting today or at least not considering a local upgrade.
>
>
>
> _______________________________________________
> sakai-core-team mailing list
> sakai-core-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>   Steve Swinsburg <steve.swinsburg at gmail.com>
>  June 16, 2014 at 7:16 AM
>
> That was just an off the top of my head example. Some footnotes would be
> good for the definitions. Maybe the following draft words:
>
> Supported would be "We have performed extensive QA using these browsers.
> Our developers use these browsers every day and test against them, and our
> QA team focus their efforts on testing in these browsers."
>
> Partial support could be "We have only performed limited QA on this
> release with these browsers. Some features may not work 100%. Please file
> any bugs at jira.sakaiproject.org".
>
> Unsupported could be: "We have not performed any QA on this release using
> these browser. Any bugs discovered using these browsers will not be fixed.
> We encourage you to upgrade your browser as the first step towards
> resolution".
>
>
>
> _______________________________________________
> sakai-core-team mailing list
> sakai-core-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>   Matthew Buckett <matthew.buckett at it.ox.ac.uk>
>  June 16, 2014 at 4:40 AM
>
> I like the nice short lists. Could we have a footnote about what they mean?
>
> Does partial support mean we have features that don't work or that we
> don't test and so it might all work but we don't know.
> Does unsupported mean it might work, but we won't fix it if it doesn't?
>
>   Matthew Jones <matthew at longsight.com>
>  June 13, 2014 at 1:09 PM
> I really don't like saying "you should be safe with " as it's more like
> "Sakai is actively used and tested with the latest versions of ".
>
> Nowadays in the browser world if you aren't on the latest Safari/IE or
> doing auto updates in Firefox/Chrome then you aren't using the same version
> as everyone else.
>
> But whatever ya'll like!
>
>
>
>   Neal Caidin <neal.caidin at apereo.org>
>  June 13, 2014 at 1:06 PM
> I made a couple of grammatical changes and want to make sure the meaning
> has not altered.
>
> Sakai 10 is designed to work with modern browsers. You should be safe with
> the latest versions of Firefox (Mozilla), Safari (Apple), Chrome (Google),
> and with IE 11 (Microsoft Internet Explorer aka IE). Sakai 10 is set to
> maintain compatibility with IE 11 (SAK-26036). Sakai  10 may work on IE 10,
> IE 9 and  IE 8. Sakai does not work with IE 7 and earlier.
>
> https://confluence.sakaiproject.org/display/QA/Sakai+10+Browser+Support
>
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20140616/fc190c3c/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1226 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20140616/fc190c3c/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1251 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20140616/fc190c3c/attachment-0001.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20140616/fc190c3c/attachment-0002.jpg