Hi Patrick,
I need to address a couple of points you write:
I have been reporting all issues concerning typo3_src-x.x.x.tar.gz here because this place is for me the first contant to report bugs.
This is becoming less and less the case for the average bug that you may encounter. In recent years TYPO3 started using more and more external dependencies instead of custom inventions, which means that the shipped source archive actually contains (more and more) code from third parties. We will of course be happy to receive the information that the bug exists and investigate, but if the bug isn't in TYPO3 source code it may happen that we refer to that and simply close the issue. This is the case where suggesting a patch again is not helpful. To be completely frank: you, as a user, should have checked those links that were given and preferably should also have checked the issue tracker of Fluid for updates on that particular issue.
However by telling people to go elsewhere, you achieve that they stop reporting stuff.
I don't think that's the average reaction. And I sincerely don't think that it's wrong to point to third parties' issue trackers and say "watch for issue status here".
Bugs are being fixed somewhere, but the fix is not being pulled for months.
This is true, but three other things are also true:
1. The third party dependencies of TYPO3 get updated automatically if you use composer.
2. When you do not, the dependencies are locked to whichever version is in composer.lock of TYPO3 itself. Those are the ones that ship in the archive and the archives are final.
3. If we indiscriminately update all third party dependencies with every release we risk breaking a TYPO3 release with no rollback like you could do on composer, therefore we do need to process these carefully and that takes longer.
My overall recommendation for this point is: use composer. Then you decide when/where you wish to update these third party dependencies and do not depend on gatekeeping/processing of a single team.
It is my opinion that either TYPO3 will get temporary patches to fix such issues temporarily until new versions of the affected patches are being pulled or that the pull frequency is increased.
I personally don't think that's a reasonable expectation, that TYPO3 should provide class overrides or forked versions of any third party library for every potential bug. That's an obligation I would not put on any open source project anywhere.
I have to repeat the recommendation to use composer here: this makes it a non-issue. With composer you yourself can even do things like apply pull requests to your installation for those extreme-priority fixes. It really means your experience can be improved if you value immediate updates to all dependencies and perfect control over versions being installed.
Honestly that kind of bugs I stumbled over leave quite a bad feeling.
I'm sorry to hear that - I can't speak for your other experiences but this specific issue was not taken as high priority (hence the six-month wait) because 1) it has not been frequently experienced by a lot of users, 2) the warnings were visible only in Development context or logs, and 3) applied only to a very specific use case which has a large amount of possible workarounds.
But you are the wrong guy to write this to.
Actually, I'm one of the right people to write this to. I'm one of the maintainers of the external Fluid repository so I can provide you with insight from both sides. I read and acknowledge your criticism of the main complaint - the speed with which this patch is being processed - but I also provided an explanation and backgrounds for the decisions.
So I will write to Olivier as I love TYPO3
I'm sure Olivier can help with the user experience and expectation management aspects, and definitely he would appreciate feedback which he always collects, but don't take this the wrong way: he does not dictate the development or shipping strategies. And we all love TYPO3 (or we wouldn't have spent a decade working with it) ;)