Making upgrades, from point of view of editing spec file, quite painful and hard to read. (Not talking about packages producing tons of libraries in deep private directories, like perl or python packages.) You can run rpmdiff to see SONAME changes.

Changing guidelines does not change spec files. AutoQA run by bodhi is better place.

Actually I don't understand what's good for: In rawhide, upgrade to incompatible version is standard part of life cycle, such upgrade in released version goes through testing which gets negative karma and a lot of nag-mails ''broken dependency'' giving time to maintainer to unpush the build.

I think maintainers should handle soname bumps in a coordinated way in Rawhide as well.

The FPC does not support this approach to solving this problem, we'd rather see some sort of automated detection of the case where the major revision of a library's sover changes in a new package build (rawhide) or a new update push (updates-testing), and notification to the packager (and devel@).

We will be opening a ticket with Fedora Infrastructure to enable that feature, as it should be possible with fedmsg/datanommer.

fwiw, I'd like to voice my support, even if I'm in the minority.

Having been bitten by others' unnoticed soname bumps in the past, my penance for them has usually been to flex some provenpackager muscle to remove the globs to adhere to essentially what was proposed here.