Bug 204584

Summary: RFE: Public "dashboard" of status of Rawhide.
Product: [Fedora] Fedora Reporter: Norm Murray <nmurray>
Component: distributionAssignee: Will Woods <wwoods>
Status: CLOSED CANTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: cweyl, jonstanley, wmealing
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-11 02:08:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Wade Mealing 2006-08-30 07:09:57 UTC
Description of problem:

I'd like to know if there are any show stoppers in the current rawhide. Many of
us don't attempt an install every day, but wish to clean our system from cruft
before reporting bugs.  

Usually, I do a fresh install to confirm these problems.  Sometimes, the rawhide
tree is unable to even be installed.  So, what would be -really cool- is to know
the status of the current tree.  

Can it be installed? Does X11 start, I'm sure that this could be tested as part
of RHTS.

Comment 1 Jeremy Katz 2006-09-06 05:36:25 UTC
These are reasonable suggestions, but outside the scope of anaconda

Unfortunately, the devil is in the details and I expect it's not as easy to do
as one would hope :/

Comment 2 Will Woods 2006-09-19 14:25:47 UTC
This is a goal of mine, but the timeline is pretty fuzzy right now.

We already have various automated test systems (KATE, RHTS, etc.) that fire
whenever a new tree is built, and do dozens of automated installs.

We need to improve those systems to give more useful results, and then find a
way to distill/summarize those results into a nice rawhide dashboard.

Like Jeremy says, though, the devil's in the details.

Comment 4 Jon Stanley 2008-04-23 20:28:40 UTC
Adding FutureFeature keyword to RFE's.

Comment 5 David Wilson 2008-04-26 21:40:49 UTC
It sounds like a database of success / fail options for the programs with a
platform / hardware list and contact info with a link to bugzilla for problems
found would be doable.  Total success / fail statistics from the database might
be useful.

Comment 7 Wade Mealing 2014-11-11 02:08:47 UTC
Closing, if people cared this would have more comments or been done by now.