There are few problem reporting application (mechanisms)
- Name: Jiri Moskovcak
- Email: firstname.lastname@example.org
- Targeted release: Fedora 16
- Last updated: 2011-07-11
- Percentage of completion: 20%
Benefit to Fedora
Unified user interface makes it easier for users to use it. Unifying the reporting backend will also mean that the config data is shared and users have to setup their credentials (like bugzilla name/password) only once.
The new reporting library will provide the same API as did the old backend (concerns only python programs - Anaconda, setroubleshoot, python-meh) so the change should be transparent without any change in the code. The only change (not required to make it work) would be to change the spec file to require the new library instead of the old one.
How To Test
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)? 1. How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.? 2. What specific actions do I perform to check that the feature is working like it's supposed to? 3. What are the expected results of those actions? -->
The bug reporting UI will change for:
- Anaconda uncaught exceptions
- setroubleshoot reports
- firstboot uncaught exceptions
"None necessary, revert to previous release behaviour."
Comments and Discussion
- See Talk:Features/YourFeatureName
- or email@example.com