Evergreen Bug Squashing Days
The Evergreen community has been holding bug squashing days several times per year since August 2014.
The goal of bug squashing days is for contributors and volunteers to commit the entire day to the following activities:
Testing bugs that have pullrequests
General bug wrangling activities (confirming bugs, marking duplicates, etc.)
Pushing bug fixes into Evergreen (for core committers)
Next Bug Squashing Days: February 27, 2017 - March 3, 2017
(In the past, bug squashing days have taken place on a single day, but many problems are not entirely resolved, tested, and accepted within a single day, so as an experiment we are going to set aside a week. Participants do not have to participate every day for the entire week.)
The goal of Bug Squashing Day is to get as many patches created, tested, and pushed into master as possible.
To avoid duplication of effort, add yourself to the "Assigned To" field in the Launchpad bug before working on it. If you're new to contributing code, see our code contribution guidelines.
Need help deciding which bugs to fix?
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 early 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 after submitting the Sandbox request.
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 that says "I have tested this code and consent to signing off on it with my name, [enter name or consistent alias] and my email address, [enter email address]."
Add a signedoff tag to the LP bug.
Remove yourself from the "Assigned To" field.
If you discover problems when testing, add a comment to the Launchpad bug.
Bug Wrangling Activities
Confirm new and triaged bugs
. Anyone with a Launchpad account has the ability to mark a bug as confirmed.
Check that old bugs
are still relevant to newer releases.
Merging Bug Fixes
Previous Bug Squashing Days