A lot of the static code analysis results are misfires because (among other things):

• there is no type hinting of the actual model or view type when getting an object using the controller's getView / getModel or the MVCFactory's createView / createModel methods
• HTMLHelper::_() is meant to take a variable number of arguments with a variadic operator in the second argument which throws static analysis off
• View templates do not have type-hinting for which object $this refers to
• Whenever an application object is used the variable's inferred type is almost always ApplicationInterface, not even CMSApplication, making static code analysis complain about missing methods, properties and so on
• There is not a single core or core component table having concrete properties for the database fields or even @property PHPdoc annotations. This is something we should REALLY fix to get rid of CMSObject usage in there a.s.a.p., see the PRs on the subject by me and George.

There are many variations of the same all over the place.

Most of these issues can be solved with type-hinting comments, some of them by introducing concrete properties. Some issues are core CMS, some issues are Platform.

Here are my questions:

• Can we file PRs for core issues if they are only adding PHPdoc comments even in patch releases and if so, who should we tag to review them? I am really annoyed by these issues and I'd love to fix (some of) them but I've been reluctant because they are touching high churn code and I don't want to be stuck merging changes in a PR's branch for six months :)
• Are we going to introduce concrete properties in tables or should we just go gang-ho and add @property declarations? Both methods are valid, both work now and with the proposed PRs for removing CMSObject
• If something is in the Platform do we make a PR to the platform and, if so, should we only expect the merged PR to be used in the next minor or the next major Joomla version? (if so, which one, major or minor?)

Thank you in advance.

In the last 2 years a lot of improvements have been made in this regard and this issue is not current anymore. To answer the questions of @nikosdion:
Yes, we can create PRs which only add PHPdoc comments. You don't have to tag anyone, they are normal PRs and will be handled by the maintainers among others. I've created several PRs to fix this stuff and it might need some time, but the stuff gets done eventually.
I don't know about the properties in the table objects. Lets see what 5.3/6.0 will bring.
Issues in the platform should be fixed in the platform and normally will be updated in the CMS with the next minor release. In some cases it might even be updated in a patch version.