On Sunday 11 December 2005 11:17, Holger Levsen wrote: > Please do bug me (even with CC:ing) when there is something to test on > oldworld. At least I'll be able (=have time) to test by booting some > kernel images... Should I test 2.6.14 "now" or wait til .15(rc) ? Well, > I wont be able to test before the 20th anyway... but please ping me, if > there is oldworld stuff to test. In general it would be great if you could do semi-regular tests. I try to do the same for x86 and sparc. For sparc I generally only do them on kernel changes and when I know there have been changes in udebs or for example parted, bootloaders that might impact sparc installs. > Frans, I've put my name into /installer/doc/devel/testers.txt and > updated the release-checklist there as well. Besides being unsure, if > prep/nubus/apus and the IBM CHRP machines would benefit from a floppy > testcase, I'm also not convinced that having the checklist there is > really as useful as it could be. (The file is too static and too well > hidden ;) The release-checklist is really only intended to be used when actually preparing for a release, not as a permanent record of status and issues. If you want to do something like that for (oldworld) ppc, maybe a wiki page would be better suited. I'd suggest you include a method to indicate when the last test was performed and what image was used. There is of course also [1] to register (temporary) issues with the daily builds. Cheers, Frans P.S. Congratulations on your new job as kernel maintainer :-) [1] http://wiki.debian.org/DebianInstallerToday
Attachment:
pgpRMdvhT3ghq.pgp
Description: PGP signature