Re: Release criteria proposal: partial kickstarts

--===============3576846742550741824==
Content-Type: multipart/alternative; boundary="0000000000004d31c60650afa810"

--0000000000004d31c60650afa810
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 20, 2026 at 11:35=E2=80=AFPM Adam Williamson <adamwill@fedorapr=
oject.org>
wrote:

> "Partially attended installation
>
> If prompted to perform a scripted installation with a configuration
> that is only partially complete, the installer should accept the
> configuration elements that are provided and prompt for interactive
> completion of the missing elements."
>

This sounds good to me in general. We could get more defensive and use
e.g. "the installer should accept the configuration elements that are
provided (where it makes sense) and ...". Because some configuration might
not make sense without some interactive decision first, which might
override the scripted configuration, trigger a question dialog, etc.

But we should definitely approach the Anaconda team with this as well.
There might be some usage cases where the criterion doesn't make sense, or
would be too broad, etc.

--0000000000004d31c60650afa810
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><div dir=
=3D"ltr" class=3D"gmail_attr">On Mon, Apr 20, 2026 at 11:35=E2=80=AFPM Adam=
 Williamson &lt;<a href=3D"mailto:[email protected]">adamwill@fedo=
raproject.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">
&quot;Partially attended installation<br>
<br>
If prompted to perform a scripted installation with a configuration<br>
that is only partially complete, the installer should accept the<br>
configuration elements that are provided and prompt for interactive<br>
completion of the missing elements.&quot;<br></blockquote><div><br></div>Th=
is sounds good to me in general. We could get more defensive and use e.g.=
=C2=A0&quot;the installer should accept the configuration elements that are=
 provided (where it makes sense) and ...&quot;. Because some configuration =
might not make sense without some interactive decision first, which might o=
verride the scripted configuration, trigger a question dialog, etc.</div><d=
iv class=3D"gmail_quote gmail_quote_container"></div><div class=3D"gmail_qu=
ote gmail_quote_container"><br></div><div class=3D"gmail_quote gmail_quote_=
container">But we should definitely approach the Anaconda team with this as=
 well. There might be some usage cases where the criterion doesn&#39;t make=
 sense, or would be too broad, etc.</div></div>

--0000000000004d31c60650afa810--


--===============3576846742550741824==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnRlc3Qg
bWFpbGluZyBsaXN0IC0tIHRlc3RAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKVG8gdW5zdWJzY3Jp
YmUgc2VuZCBhbiBlbWFpbCB0byB0ZXN0LWxlYXZlQGxpc3RzLmZlZG9yYXByb2plY3Qub3JnCkZl
ZG9yYSBDb2RlIG9mIENvbmR1Y3Q6IGh0dHBzOi8vZG9jcy5mZWRvcmFwcm9qZWN0Lm9yZy9lbi1V
Uy9wcm9qZWN0L2NvZGUtb2YtY29uZHVjdC8KTGlzdCBHdWlkZWxpbmVzOiBodHRwczovL2ZlZG9y
YXByb2plY3Qub3JnL3dpa2kvTWFpbGluZ19saXN0X2d1aWRlbGluZXMKTGlzdCBBcmNoaXZlczog
aHR0cHM6Ly9saXN0cy5mZWRvcmFwcm9qZWN0Lm9yZy9hcmNoaXZlcy9saXN0L3Rlc3RAbGlzdHMu
ZmVkb3JhcHJvamVjdC5vcmcKRG8gbm90IHJlcGx5IHRvIHNwYW0sIHJlcG9ydCBpdDogaHR0cHM6
Ly9mb3JnZS5mZWRvcmFwcm9qZWN0Lm9yZy9pbmZyYS90aWNrZXRzL2lzc3Vlcy9uZXcK

--===============3576846742550741824==--