Proposal: Rawhide tracker bug

[Kevin Fenzi]

Greetings. 

I'd like to propose we create a rawhide tracker bug.

Probibly name it: RawhideBlocker 
(But I don't care what colour the bikeshed is)

This bug would be used for the following types of bugs against the
'rawhide' version: 

- bugs that prevent the daily rawhide compose from completing. 
  (In practice this can only be a small subset of packages used for the
  compose in the chroot)

- 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. 

- 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. 

(we could add additional criteria as we go)

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. 

This would of course require people watching the bug to note any bugs
added to it that are NOT in the above criteria, but I think that should
be easily possible with enough people watching the bug. 

Thoughts?

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/test/attachments/20130311/7e5a05c9/attachment.sig>