On Wed, Apr 22, 2015 at 04:50:39PM +0200, Bernhard Voelker wrote: > On 04/22/2015 04:20 PM, Ruediger Meier wrote: > >On Wednesday 22 April 2015, Karel Zak wrote: > >> I hope so:-) Next time it would be nice to detect and fix such bugs > >> in major release or in .1 ... we need a way how to motivate users > >>to use -rc releases (t-shits, beers? ;-) > > > >Hehe, maybe the only way is like we have it right now. 2.xx and 2.xx.1 > >are the real rc1 and rc2. The distributors have to learn to use 2.xx.2 > >only ;) > > Isn't there a cross-platform CI system somewhere? > ... okay, http://build.opensuse.org/ is one, but it usually > doesn't track upstream changes. There's also things like > Hydra (http://hydra.nixos.org/) ... but this only seems to > cover i686 and x86_64. We already use https://drone.io/github.com/karelzak/util-linux and https://travis-ci.org/karelzak/util-linux both connected to github, but for ppc64 and s390 I use machines in Red Hat labs and during -rc1 I usually use Coverity analyzer. It's also possible to use Fedora/Suse build farms, but we don't execute all the tests (especially tests where is necessary root perms) by default. Anyway, this is no problem, the problem is real life testing. Fortunately, I can push unstable stuff to Fedora Rawhide :) Karel -- Karel Zak <kzak@xxxxxxxxxx> http://karelzak.blogspot.com -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
