Howard Miller

What do you mean "it doesn't work"?

If there's no upgrade key then upgrade will proceed without it. If there is one then you'll get asked for it. I'm not sure what the other possibilities are.

And just for completeness, what version of Moodle are you running / upgrading to?

I'm not sure that I think the process is particularly complex... I use git, pull requests and so on all the time as well. It's just another obstacle in a busy day.

Ok - I was just venting (my $00.02) but I'm not difficult or obstinate enough not to give it a fair try....

I wanted to add something....

I have always encouraged my colleagues (and anybody else who would listen to me) to contribute to the developer documentation. Developers don't like writing documentation and this was always an uphill struggle. Much nagging required. However, "if you can figure that out and get it working, please add it to the docs".

Now, what am I supposed to say.... "Well... clone the git repo, install some application, learn how to use it, make the changes, submit the pull request. No, I have no idea if it will be accepted". Complete waste of time.

Maybe I'm being naive and the whole point was to prevent devs working outside of Moodle HQ from contributing to developer documentation. However, if that was the case, HQ need to step up and do a LOT of work on those docs.

So, your moodle site "lives" at /srv/http/moodle on your web server?

There's been a few reports of issues with this new 'slim' routing feature and I don't think it's at all clear what's gone wrong (yet).