Comment 4 for bug 688112

I think there are two seperate issues here.

One is that the sorting should be "version first, then usefulness" (currently its only sorting by usefulness
and then submission date afaict).

The other one is that our current schema forces origin and distroseries. I don't think we can omit origin
otherwise reviews for ppa:firefox-really-badly-packaged will be showing the really-well-packaged-main-ubuntu
firefox reviews (and vice versa).

If we change distroseries to version version I think we need to ensure there is a additional parameter in the
api so that the version that the user has (either installed or as candidate) is submited and no reviews for
newer versions are shown if those are not installable. Otherwise the user will see reviews about new features t
hat are not available for his/her version. Especially important for fast moving stuff (unity comes to mind).

I'm not sure we need to change the API to include a versionnumber in the query though instead of the distroseries.
For the main archive we know what the latest version for natty (we can ask LP). For launchpad PPAs we can do the
same. We need to "carry over" previous review when a new distro series opens though (that is a burden).

I have no strong feelings about versionnumber vs distroseries, I do think that for some apps it will make a difference
on what release they run because of compat issues. The removal of the notification area comes to mind in natty. So
a app relying with the nofitcation area in 10.10 will get very different reviews in 11.04. Its not a very common thing
I'm sure, but I don't think the amount of cases like this is zero.