1. /boot on Btrfs grubby (83 comment, 2.5+ year, booger we can't flick off) https://bugzilla.redhat.com/show_bug.cgi?id=864198 The first one is fairly appalling because it's a.) old, b.) there's a tested patch, c.) we're in contempt of our own lament for contributors when b and c and it still doesn't get fixed; and d.) Josef openly called for replacing grubby with something that works, seeing as openSUSE, Ubuntu, Debian, (does anyone else?) don't have this problem. 2. Custom partitioning does not allow convenient removal of volume including snapshots (btrfs, LVM) https://bugzilla.redhat.com/show_bug.cgi?id=1185117 This might seem like it snuck up on us, but I predicted it would become a problem in two different RFEs one of which is ~18 months old. [1] Neverthless, openSUSE's default highly snapshottycentric behavior enhances this problem; but so does Docker on Btrfs; and now in systemd-219 it's using Btrfs snapshots for container cloning. So these things are going to continue coming out of our ears. PROPOSAL: QA doesn't have an exception policy. If a bug is a blocker under the current criteria, they block release. Done. Proposal is to submit them to FESCo to a.) acknowledge they're blockers; b.) grant an exception for blocking Fedora 22 on the basis that they're not crazy showstoppers for many people yet; and c.) should be tagged as blockers for Fedora 23, and as such there are no excuses for them not getting fixed by then. Why? Process. I think it's better to adhere to process, and thus far there's a rather obvious resistance to fixing these two bugs in the Fedora 22 time frame. So here's an alternative approach. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1015657 https://bugzilla.redhat.com/show_bug.cgi?id=1022316 -- Chris Murphy -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
