From Fedora 26 onward, as well as anaconda's own partitioning flows ('automatic' and 'custom', as we usually refer to them) you can ask anaconda to run blivet-gui and do your partitioning in that.
As this option is presented with about equal important to 'automatic' and 'custom', we probably ought to treat it with equal importance for testing. So we should ensure the release criteria cover it.
This shouldn't be too difficult, it's probably just a case of finding all the places the criteria currently refer to 'custom partitioning' and adjusting them to clarify that the requirements apply to both anaconda's built-in 'custom partitioning' and using blivet-gui. Unless someone thinks we should have different requirements between those two.
See also #503 , for adjusting the validation matrix and test cases.
Instead of adding a footnote to each criterion mentioning custom partitioning, maybe we can add a definition of the term at the beginning of Alpha Release Requirements, the same way as we define what release-blocking desktop and release-blocking image is?
release-blocking desktop
release-blocking image
Metadata Update from @adamwill: - Issue assigned to adamwill
I'm gonna say this change fixes this.
Metadata Update from @adamwill: - Issue close_status updated to: Fixed - Issue priority set to: critical - Issue status updated to: Closed (was: Open) - Issue tagged with: criteria
Log in to comment on this ticket.