English
How To Test
*REQUIRED FOR SYSTEM-WIDE CHANGES*
This does not need to be a full-fledged document.
Describe the dimensions of tests that this change implementation is expected to pass when it is done.
If it needs to be tested with different hardware or software configurations, indicate them.
The more specific you can be, the better the community testing can be.
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
A good "how to test" should answer these four questions:
What special hardware / data / etc. is needed (if any)?
How do I prepare my system to test this change? What packages need to be installed, config files edited, etc.?
What specific actions do I perform to check that the change is working like it's supposed to?
What are the expected results of those actions?
User Experience
If this change proposal is noticeable by users, how will their experiences change as a result?
This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
Describe what Users will see or notice, for example:
Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
Libreoffice is one of the most commonly installed applications on Fedora Linux and it is now available by default to help users "hit the ground running".
Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora Linux users being the most relaxed users of any operating system.
Dependencies
*REQUIRED FOR SYSTEM-WIDE CHANGES*
What other packages (RPMs) depend on this package?
Are there changes outside the developers' control on which completion of this change depends?
In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?
Other upstream projects like the kernel (if this is not a kernel change)?
Contingency Plan
*REQUIRED FOR SYSTEM-WIDE CHANGES*