Hi Martin,
The process for initial scheduling has been the same for quite some time. The difference between those two entries is the versions in which the problem can be reproduced. Problems working on an earlier version and then breaking on a new one are considered as breaking and by default they are scheduled to the next available version, which in this case is 6.4.0 Release d.
Other problems are usually left unscheduled until we have some general plans for priorities of a particular future version, in which case we group related entries that fall within the set goals to this version.
Regarding your particular tracker entry, I'll be happy to discuss it with the developers and those handling the scheduling to see if we can squeeze it in on an earlier release. We'll post update here on this thread, or on the tracker entry itself, if there are any updates. In some cases we do find a workaround and if we do, we will also post it here or on the tracker entry itself, or both.
P.S. I see that in my earlier post, I accidentally linked the demo application directly instead of the tracker entry. This has now been fixed.
Palli