This has been already discussed before [1], but the discussion died down. Here's an updated proposal.
Change the following:
From: "When using a release-blocking dedicated installer image, the
installer must be able to use either HTTP or FTP repositories (or both)
as package sources. Release-blocking network install images must default
to a valid publicly-accessible package source."
To: "...must be able to use HTTP(S) repositories as package sources..."
Also add a new footnote:
"Covered repository types
This criterion only covers direct repository URLs ("baseurl"), and doesn't cover mirrorlist or metalink URLs."
From: "The installer must be able to download and use an installer update image from an HTTP server."
To: "...from an HTTP(S) server."
From: "When using the dedicated installer images, the installer must be
able to use HTTP, FTP and NFS repositories as package sources."
To: "...must be
able to use HTTP(S) and NFS repositories..."
Also update its footnotes in the same spirit.
Also add a new footnote:
"Covered repository types
This criterion only covers direct repository URLs ("baseurl"), and doesn't cover mirrorlist or metalink URLs."
It will also have an effect on our test cases:
Rename to QA:Testcase_install_repository_HTTP_graphical
Update the contents by replacing HTTP with HTTP(S) and dropping FTP mentions.
Rename to QA:Testcase_install_repository_HTTP_variation
Update the contents by replacing HTTP with HTTP(S) and dropping FTP mentions.
Update the contents by replacing HTTP with HTTP(S).
Please approve or comment, thanks.
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
