Evergreen Bug Squashing Week

Next Bug Squashing Week

March 4-8, 2019

Overview

1. Launchpad

Launchpad is the bug tracking system used by the Evergreen community. Register for a login so that you can participate in bug reporting and testing.

2. Testing

You may participate in Bug Squashing Week by…

Testing bugs that other people have reported in order to confirm them.
Testing bug fixes that have the pullrequest tag to be sure that they work.
Providing additional feedback on bugs that have not yet been fixed.
Submitting new bug fixes.
Submitting documentation updates.
Pushing bug fixes into Evergreen (for Core Committers only).

3. Sign-Offs

If you test a bug fix that someone else has created and find that it works as described, you can sign off on it:

Activities

The goal of Bug Squashing Day is to get as many patches created, tested, and pushed into master as possible.

Reporting Bugs and Leaving Feedback on Bugs

Evergreen bugs are tracked in Launchpad (https://bugs.launchpad.net/evergreen). Learn more about how to access and use Launchpad from Mary Jinglewski and Andrea Buntz Neiman's presentation at the 2018 Evergreen International Conference: Open Slideshow

Fixing Bugs

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?

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
See the separate Documentation Needs list for a variety of tasks not on Launchpad.

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 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:
1. 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]."
2. Add a signedoff tag to the LP bug.
3. 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.