On Fri, 2015-03-13 at 13:36 -0600, Chris Murphy wrote: > http://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria > > The only final release criteria pertaining to disk encryption has to > do with keyboard support, so skipping that. For beta there is only > one criteria applying to encrypted disks, and it reads: <snip> First point: note that for Final we still have the catch-all criterion I hate more and more as time goes on: "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration." which more or less means 'everything must work', which is clearly kind of silly, and badly needs rewriting. If we were to interpret it literally, it would already cover any kind of encryption support the installer offers. If we pretend we don't have that criterion... I kinda like the direction you're going in here, but I find the wording awkward. How about something along these lines? == Guided partitioning == When using the guided partitioning flow, the installer must be able to: ... * Correctly display the locations and sizes of existing storage volumes and remove them to free up space, at the user's direction ... == Custom partitioning == When using the custom partitioning flow, the installer must be able to: * Correctly display, remove, and assign mount points to existing storage volumes of the supported types (requiring entry of the encryption passphrase, for encrypted volumes) * Correctly display the locations and sizes of, and remove, existing partitions of other types * Create and assign mount points to new storage volumes of the supported types * Remove a planned storage volume from the planned layout * Reject or disallow invalid disk and volume configurations without crashing. footnote: Supported storage volume types Supported storage volume types are btrfs, xfs and ext4 filesystems - including LUKS-encrypted filesystems - residing on: * Plain partitions * LVM logical volumes (including thinly-provisioned LVs) * btrfs volumes and sub-volumes * Linux software RAID-0, RAID-1, and RAID-5 sets * Reasonable combinations of the above (e.g. LVM-on-RAID) If we're going to touch this stuff, though, maybe we should try to kill the horrible Final criterion, decide what (if anything) beyond the above we want to support by Final, and maybe split the requirements a bit between Beta and Final or allow some workarounds / exceptions at Beta and stuff. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
