On 9/7/05, Daniel Veillard <veillard@xxxxxxxxxx> wrote: > Can't basic bootup of kernels on i386 uniproc machine be tested before > pushed to rawhide, channels, mirrors and users ? http://www.livejournal.com/users/kernelslacker/23505.html Are you going to provide the spare box to sit inside the RedHat fence line to watch for new kernel builds in redhat's buildsystem,test boot itself, and then report back in a scripted/automated fashion so that the kernel build can be removed? Until the binary build comes out in rawhide its not available for public consumption any other way from redhat's build system. So if you come up with a solution for this, it will have to be implemented completely within the redhat fenceline. > > Similary if some change broke anaconda, can we backtrack that change > in the sake of keeping an installable dist, my servers are pulling everyday > new version of boot images and anaconda stuff which are know to not work, > and users are trying to use them while again we know they don't work. Similarly are you going to provide the redhat internal hardware to do the scripted anaconda regression tests? -jef -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-devel-list
