> - bugs that break the rawhide buildroot. In practice these are > usually > noticed pretty quickly and the offending build is just untagged > until > it can be fixed, but there could be cases where the fix is more > complex and has a bug associated with it. For those of us who are not skilled in building a release, what does this exactly mean? I can imagine bugs that prevent compose (no package repo created), but this one could deserve a closer explanation. > > - bugs that cause a large number of rawhide systems to be unbootable. > This would be things like dracut or kernel or glibc or systemd > issues > that cause most rawhide installs to fail to boot. What about broken gdm, does it fall into the category? Should "critical path packages" be also covered by this tracker bug? (Firefox broken, pulseaudio broken, gnome-terminal broken, yum broken, ...) > The idea is that folks running rawhide could watch this bug and more > easily see issues that are major as they appear and know when they > got > fixed. They could also add bugs to this and developers could see that > the bug is high priority and more resources could be brought to bear > on > it. Additionally we could gain some insight into how often these kind > of bugs happen and how long it takes to fix them. I support this a lot. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
