This thread is about how to handle feature requests and now you are mixing with bugs. A different battle even if in bugzilla they are so close. Still:

The common denominator of these bugs seems to be: won't be fixed in Diablo but won't be a problem in Fremantle because XYZ is refactored. The teams have to negotiate between the time they invest in the old components to be discontinued or building the new components with the fixes build in. In case of doubt they move forward to the next release, yes. Hopefully releasing early SDKs helps rising those issues before, while the teams are still investing most of their time in the current release.

These are enhancement requests fixed in Fremantle. Not in Diablo, again because the related components are being refactored and it would imply doing the work twice (while not doing something else new).

This is an enhancement request (potentially a bug) on a component discontinued after Diablo. The new component probably will have it integrated. Same kind of story.

So basically, all those requests will be satisfied in Fremantle even though they get wontfixes in Diablo.

Andre does his job as I do mine and others do theirs. Even if Andre is not a Nokia employee, he is being funded by Nokia and gets a good salary to be as efficient community bugmaster as he indeed is. As said above about the feature requests, in order to have a Brainstorm working the product managers need to be directly involved, agreed.