dev:bug_squashing:2014-08-26
This is an old revision of the document!
Table of Contents
August 2014 Evergreen Bug Squashing Day
Date: August 26, 2014
Time: Whatever time you work on Evergreen
Activities
The goal of Bug Squashing Day is to get as many patches created, tested, and pushed into master as possible.
Fixing Bugs
Need help deciding which bugs to fix?
- Find dusty bugs by looking at the oldest non-wishlist bugs on Launchpad
- Start with the bugs that are most important to users by looking at the non-wishlist bugs with the most heat
- Try these bitesize bugs
Testing Bugs
These Evergreen bugs with pullrequest tags are ready for testing. According to community guidelines, each piece of new code needs to be tested and get a sign-off from somebody else before it can be merged into Evergreen
Testing involves the following steps:
- Loading the code on a non-production server. If you cannot load code or cannot work with a local tech person to load code, you can submit a request for a Bug Squashing Day Sandbox. Please note, the community will have a limited number of Sandboxes available and may not be able to accommodate all requests. Please submit your request by the end of the day Friday, August 22 to give us time to get the Sandbox ready.
- To avoid duplication of effort, add yourself to the "Assigned To" field in the Launchpad bug.
- If your testing finds the bug fix works as expected and does not break other functionality, sign off on the code or add a comment to the Launchpad bug saying that it passed your testing. Add a signedoff tag to the LP bug and remove yourself from the "Assigned To" field.
- If you discover problems when testing, add a comment to the Launchpad bug.
dev/bug_squashing/2014-08-26.1408311837.txt.gz · Last modified: 2022/02/10 13:34 (external edit)