As @christianm already said, much of that is true.
Including, and that is where I again stress we need help: the dev codebase lacks testing. And often enough people come across something and do not report an issue afterwards. And fixing those things could need help, too.
Anyway, can you explain the first example or point me to an issue about it? I checked and cannot find what seems to be missing… As for the other two: 1) it should just go to the parent node, that is what it did for "ages" now. No more? 2) Is this what we fixed with 2.3.8?
Again: if there are bugs, do not "report" them here, on twitter or via Slack–create issues instead. And when talking about bugs, link to the issues. If no issue exists yet, go to step 1.
As far as "fixing the issue over the next month" goes, not sure there is any value in promising anything. As already pointed out, with (experienced) help, maybe something can be done. But it seems everyone has too much work, all the time… That being said: any help, suggestions, ideas, PRs, new tests, infrastructure improvements are welcome!