To me it looks like none of them was a pure bugfix release, all mention some new features

http://blog.qupzilla.com/2015/11/qupzilla-189-released-with-new-logo.html
http://blog.qupzilla.com/2015/10/qupzilla-188-released.html
http://blog.qupzilla.com/2015/10/qupzilla-187-released.html

So according to 
https://wiki.mageia.org/en/Updates_policy#Version_Policy
qupzilla-1.8.9 cannot go into updates, so changing the Component of this report to Backports.

CC'ing the maintainer, but assigning to pkg-bugs mailing list, because:
* I do not know whether backport request should be assigned to the maintainer of a package, or treated like package requests
* the maintainer seems MIA, anyway

Component: RPM Packages => Backports
Assignee: bugsquad => pkg-bugs
CC: (none) => marja11, matteo.pasotti

I should have assigned to Matteo, sorry

https://wiki.mageia.org/en/Backports_policy#Steps :

Triage

    identify backport requests
    add "Backport Request: " in the bug report summary
    add the "backport" keyword
    assign to maintainer 

The maintainer can refuse to do the backport, but must give a reason :

    doesn't want to maintain it => assign the bug report back to bugsquad@mageia.org so that another packager can step in
    has a good reason for not providing this backport (policy, possible breakage...) => close as wontfix

Summary: Qupzilla 1.8.9 => Qupzilla 1.8.9 Backport Request
Source RPM: (none) => qupzilla-1.8.9
Keywords: (none) => Backport
CC: matteo.pasotti => (none)
Assignee: pkg-bugs => matteo.pasotti

I keep those as minor new features.Second thing think marja what we do to chromium all time,we update it with expection throught updates that goes with all browsers.

(In reply to Otto Leipälä from comment #3)
> I keep those as minor new features.Second thing think marja what we do to
> chromium all time,we update it with expection throught updates that goes
> with all browsers.

Aren't those security updates? 

I didn't see a security fix among the bugfixes for Qupzilla, but I may have overlooked them and my understanding that the browser updates are for security fixes, may be wrong, too.
CC'ing Akien and Luigi12, who'll know better than me.

CC: (none) => luigiwalser, rverschelde

The Chromium example doesn't apply here indeed, as those are security updates and there's no other way to do that because of upstream's development model.  The Qupzilla releases do look like bug fixes to me though, so it would be OK with our policy to update it, so I think we should honor the request to update it.  I would do it now, but I don't have a reliable internet connection at the moment, so I'll do it next week if nobody beats me to it.

Component: Backports => RPM Packages
Source RPM: qupzilla-1.8.9 => qupzilla
Keywords: Backport => (none)
Summary: Qupzilla 1.8.9 Backport Request => Qupzilla 1.8.9 Update Request

Thanks david and yes you are right with chromium there is no other way to do it.
Happy new year too to you david. :)

Updated package uploaded for Mageia 5.

Advisory:
----------------------------------------

The qupzilla package has been updated to version 1.8.9, fixing several bugs.
See the upstream release announcements for more details.

References:
http://blog.qupzilla.com/2015/10/qupzilla-187-released.html
http://blog.qupzilla.com/2015/10/qupzilla-188-released.html
http://blog.qupzilla.com/2015/11/qupzilla-189-released-with-new-logo.html
----------------------------------------

Updated packages in core/updates_testing:
----------------------------------------
qupzilla-1.8.9-1.mga5
qupzilla-core-1.8.9-1.mga5
qupzilla-plugins-1.8.9-1.mga5
libQupZilla1-1.8.9-1.mga5
libQupZilla-devel-1.8.9-1.mga5

from qupzilla-1.8.9-1.mga5.src.rpm

CC: (none) => matteo.pasotti
Assignee: matteo.pasotti => qa-bugs

Testing on Mageia 5 x86_64, seems to work fine. Did some basic browsing, ran HTML5 youtube videos, the 2048 HTML5 game.

Also enabled a couple plugins and checked that they work OK.

Whiteboard: (none) => MGA5-64-OK

Bug 16148 is still valid but apparently it's not necessarily something that must be fixed in qupzilla itself.

No it's not bug in qupzilla it use by default pixelated bitmap fonts,you can force it to use only system truetype fonts so it will look lot more better.
Every other applications suffer this too what use those bitmap fonts.

https://wiki.archlinux.org/index.php/Font_configuration#Disable_bitmap_fonts

I taked screenshot to show how it look when it use only system truetype fonts.

https://www.dropbox.com/s/cni26m0s3xole3l/qupzilla.png?dl=0

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0007.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED