> From: "Adam Williamson" <awilliam@xxxxxxxxxx> > To: "For testing and quality assurance of Fedora releases" <test@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Tuesday, January 31, 2012 1:42:30 AM > Subject: Re: New criterion for updates.img using > > On Mon, 2012-01-30 at 11:28 -0500, Petr Schindler wrote: > > I propose new beta criterion: > > > > "The installer must be able to use updates.img obtained by any > > supported way" > > > > I think, that this should be at criteria too. There are test cases > > which uses this feature - [1], [2] > > > > [1] > > https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_installation_source > > [2] > > https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_local_media > > Similar to previous: > > "The installer must be able to retrieve and use an > [[Anaconda/Updates| > installer update image]] by any supported method" > > Though this may be too broad, and we may have the problem we had with > kickstarts in F16, where some really obscure retrieval method doesn't > work and we don't really want to block the release for that. We might > want to be more specific and only support more common updates.img > deployment channels. Thank you for suggestions on this. I would require only methods for which we have test case [1] [2] and from alpha [3]. So I propose beta criterion: "The installer must be able to use an [[Anaconda/Updates|installer update image]] retrieved from removable media, remote installation source and HTTP url" [1] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_installation_source [2] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_local_media [3] https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_URL -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
