Hi, folks! We did the release blocker bug review meeting today, and one of the bugs that came up for discussion was this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1134524
The question of whether this bug is a release blocker comes down pretty clearly to the status of the Workstation network install image. That is, the image is clearly busted, so if we care about that image, we should consider the bug a release blocker.
However, the question of whether the Workstation network install image should be considered 'supported' / 'release-blocking' / whatever does not appear to be settled. As I noted in my comment:
https://bugzilla.redhat.com/show_bug.cgi?id=1134524#c2
as Workstation was originally designed it seemed clear that the answer was "no, we don't care about netinst", but things seem to have changed somewhat since then, and kalev seemed fairly receptive to blocking on Workstation netinst for F21:
<kalev> adamw: so, my take on this is that I would really like to have a single installation media for Workstation, only the live USB / dvd <kalev> but I also do understand that in some environments, the PXE boot and netinstall are necessary, especially corporate installations <kalev> what I'm envisioning in the future is that we should have a single netinstall for the whole of Fedora, where one could select server or workstation <kalev> but that's not the future we are in right now; I'll try to lobby to make this happen for F22 <kalev> but for F21, I think we'll just have to make do with what we have and make the workstation-specific netinstall work <kalev> so I don't mind having it as a blocking bug
I thought it'd be best to have a clear and publicly-recorded consensus on this, though, and ask the Workstation WG to amend the tech spec if appropriate. So: is it the case as kalev suggests that for F21 at least the Workstation network install image should be considered 'release blocking', i.e. a supported medium of the Workstation product? If so, can the tech spec be updated to reflect that?
Once there's a clear answer to this question, we'll update the release criteria appropriately and determine the blocker status of the bug.
Thanks!