Martin Dougiamas

It's about reducing work for our developers who need to work around all the bugs in the older browsers.  It's also about encouraging institutions to allow their users to upgrade, or at least support a dual browser strategy, thus improving the online experience for everyone.  Using more modern browsers is free and not exactly a risky thing technically, even if an institution for some reason wants to stick to an old OS.

We shadow Google and they dropped support last year:  http://googleappsupdates.blogspot.ca/2012/09/supporting-modern-browsers-internet.html

Note that dropping support doesn't mean Moodle won't work on those old browsers (it surely will!), it just means we won't bother too much if new bugs on those old browsers are discovered.

I don't think a forum is really an ideal place to curate a list like this.  By all means add forum links to the release notes if they are relevant though, surely that will give people the best chance of finding out this information.

All the changes in every release should always be on the release notes:  http://docs.moodle.org/dev/Releases

If anything gets missed please tell someone or add it there yourself!

It's no longer necessary to install the license in Jira Client: the license is on our server and everything just works when you connect to tracker.moodle.org.   MDLSITE-2090

Totally agree that we need to decide on this for 2.5.

I'd appreciate if you guys here could consider yourselves a task force and come up with a good recommendation for us to put in core.

Needs to be GPL-compatible obviously, and I would suggest focussing on HTML5 solutions just because of the flexibility and taking load off the server,