I totally agree. The only thing we are saying is that we will not be testing things on old browsers, not that we are purposefully breaking anything. I imagine the degradation will be quite gradual for anyone stuck on an old browser for whatever reason.
But discussion continues here: MDL-41973
I doubt 2.6 will be an official LTS from us. There are still many important things like analytics and mobile support which are being developed at this stage. 2.7 could be If development goes well.
Note that there is nothing stopping the community from volunteering to support 2.6 for as long as they like (back porting security issues etc) but there is simply no incentive for us to aid in keeping people there at the moment. We just want you to have the best functionality, the best usability and the best accessibility.
There is some info on that here http://docs.moodle.org/dev/Logging_2#Public_API ... but I hope there can be more detail added by the BACKEND team working on the spec.
However, it's worth noting that there will be no need for most Moodle code to ever access logs this way. Moodle code that currently accesses or joins to the log table (eg Recent Activity) will usually listen to events directly and capture what it needs in the most efficient format.
I also expect any really heavy future analytics processing will take place externally to Moodle.
"teacher directed lecturing" !
What? Quite the opposite! Do you know what it takes to get one of those Doctorate hats? Years of willpower and self-directed learning and discovery.
I don't see how it's nonsense., Tim.
To use your example, your statement that the question definition cache would require manually clearing every time a teacher edits a question is exactly the sort of information an admin needs to make an informed decision, based on how they use Moodle.
They may know that quiz questions are not updated in a production instance, and so it might make sense to use a local cache for it for a bit of extra speed.