On Wed, 2014-02-26 at 10:24 -0500, David Cantrell wrote: > > Yep, a lot of fun - three different file systems for free different products. > > And we are back to the question how much these products could differ - with > > limited resources we have right now - at least short term. Who can answer it > > - filesystem/kernel guys, if they are able and willing to support all > > potential filesystem, as David stated, it's possible in Anaconda but again > > the same question if the team would be able to maintain more filesystems > > support with high bar in terms of quality (even for example brtfs limited > > to bare minimum), QA... And it could be pretty confusing for users but that's > > up to us/marketing to explain that products aim specific goal and it's for > > good (if we would be able to support it - then it's for good, if not...). > > I think filesystem variance across different Fedoras really impacts QA more > than us. We already support a lot of filesystems, but the real hit is the > QA test matrix. Well, there is an indirect impact on devel. As I said, it's about what we decide is 'release blocking'. The historic approach there, and the one that's really simplest and makes most sense, is 'guided path is release blocking, custom is not'. The more choice there is on the guided path, the more release blocking codepaths we have, and the more release blocker bugs you folks get to treadmill. If, for instance, we ditched LVM thinp and btrfs from the guided path dropdown, we cut the number of potentially release blocking paths by 50% immediately. It won't necessarily cut the number of release blocking bugs by precisely 50%, but it's pretty hard to believe it wouldn't cut the number at *all*. And I know you folks get tired of the release blocker treadmill. Remember, what QA release validation testing ultimately *results in* is blocker bugs :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
