Maybe some background here from the bugmaster's point of view:

A few months ago, I started using a generic Target Milestone in Bugzilla called "5.0/+" and set this Milestone plus the status RESOLVED FIXED for reports that "will be fixed in the next update of Maemo5" (at that time).

However, Nokia surprisingly started releases like PR1.0.1 (1.2009.44-1) or PR1.1.1 (3.2010.02-8) that only contained some cherry-picked fixes which not only surprised me and made the assumption that I had written ("will be fixed in the next update of Maemo5") a lie, unfortunately. So I started writing "Will be fixed in the a future update (not necessarily the next one)".

However, that sucks too of course. So today I set at least those reports for which I absolutely know that they will be included in the future PR1.2 update to an explicit Target Milestone called "5.0/(PR1.2)".

This does NOT mean that this "Fixes in PR1.2" list is complete yet.
It's just those fixed issues that I'm sure of so far as they were fixed two weeks ago or earlier, as Nokia in the past always had 2 or 3 weeks between packaging the update internally and releasing that update for public. Those 2 or 3 weeks are used for testing, verification etc - you know, bureaucracy is slow.

Plus it also makes it easier for Nokians in maemo.org Bugzilla to set realistical Target Milestones. A bit less frustration for everybody, hopefully.

Hope that helps a bit in understanding.