On Fri, 2015-06-05 at 08:00 -0400, Stephen Gallagher wrote: > > > > and > > here is what stuck to my mind. Others are of course welcome to add > > > > what > > I have forgotten and to correct me when I a wrong. > > > > To start, we'd like to have an automated way to check the ABI > > compatibility of binaries embedded in packages that are submitted > > to > > the > > updates-testing repository. When an incompatible change[1] is > > detected, > > Just to clarify, this isn't about the karma *count*, it's about > whether > a package can be pushed to stable automatically when it reaches the > karma threshold or if it requires a conscious decision by the > maintainer to push it. This will present backwards-incompatible > changes > from going to stable *accidentally*. (There are cases where they are > permissible, such as security patches or ABI changes that are > coordinated with all their consumers). I'd prefer that ABI never breaks within a stable fedora release unless there is some special permission for it. There can be no excuse "coordinated with all consumers", because there is also software in the end user's systems where we can have no coordination. regards, Nikos -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
