Compiz Bug Management
Bring current compiz bugs to a manageable level to be able to fix underlying problems
Blueprint information
- Status:
- Complete
- Approver:
- Martin Pitt
- Priority:
- Medium
- Drafter:
- Robert Ancell
- Direction:
- Needs approval
- Assignee:
- Robert Ancell
- Definition:
- Approved
- Series goal:
- Accepted for karmic
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Robert Ancell
- Completed by
- Robert Ancell
Whiteboard
Work items:
Produce user-facing Wiki page for solving common compiz issues http://
Update Compiz triaging instructions https:/
Update Compiz apport scripts: DONE
Triage compiz bugs to manageable level (multi-day): DONE
Organise community day to check triaged bugs still occur and provide repeatable instructions: POSTPONE
2009-06-01, pitti: The outcome of this should be documentation in the wiki (debugging howtos, and writing down the desktop team bug policy).
Meeting Notes:
Goals:
- Decide on what is supported for Compiz
- Ideas for improving automation with apport / autofiling
- Wiki page:
- Users: "Your version is too old, please disable Compiz" (but say nicely)
- Triagers: How to triage compiz
- What helps upstream?
- Can we get more community involvement?
- <100 bugs for Karmic
Current State:
- 646 bugs, 565 not triaged
- Lots of attempts to handle these, very little progress
- Majority of bugs relate to video drivers
Ideas:
- Group crashers by video drivers - use for statistical analysis
- Reject all bugs using custom compiz configuration (detected with apport)
- Reject all bugs < Jaunty - Compiz will almost certainly not qualify for SRUs so these bugs are just noise
- Encourage users to disable compiz if they have problems (it's not required, try again when they have new video drivers)
- Could someone (e.g. upstream) provide a "compiz compatibility tool" that exercises the stack that compiz uses? Failures would provide good feedback for compiz/X/kernel developers.
Actions:
1. Run scripts over existing bugs and reassign FGLRX/Nvidia bugs to other packages, or don't allow them getting filed at all (UnsupportableR
2. Consider how to manage incoming bugs to keep manageable
3. Improve compiz debugging information - https:/
4. Mark pre-Jaunty bugs automatically Incomplete with request for information - close if no response
5. Let community keep bug count low
6. Pete Graner is getting the most duplicated crash - he may be able to give information
7. Close bugs with good stack traces but no duplicates for a year (with an apology)
8. Close bugs using non-standard configuration (detected by apport through gconf)
9. Close bugs using non-free drivers
10. Follow http://
* feedback / changes to bdmurray
New Compiz help page for users:
https:/
Automated scripts used in XOrg:
http://
http://
