• September 21-25: Bug Squashing Week

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. 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

More information about using Launchpad

2. Testing

You may participate in Bug Squashing Week by…

• Testing bugs with the "New" status that other people have reported in order to confirm them.
• Testing old bugs to see if they are still valid. If they are, add feedback to confirm that they are still valid in the Evergreen version you are working on. If they are not, add feedback and change the status to "Won't Fix."
• Testing bug fixes that have the pullrequest tag to be sure that they work (see Testing Bugs section below).
• Providing additional feedback on bugs that have not yet been fixed.
• Adding tags to bugs - please see the list of current official tags (as of Summer 2020).
• Submitting new bug fixes (see Fixing Bugs section below).
• Submitting documentation updates.
• Pushing bug fixes into Evergreen (for Core Committers only).

3. Sign-Offs

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

• Sign off on the code through gitor 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]."
• Git setup and signoff instructions are available on the New Developers Group page.
• Add a signedoff tag to the LP bug. (Do not remove the pullrequest tag.)

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:

1. 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.
2. To avoid duplication of effort, add yourself to the "Assigned To" field in the Launchpad bug after submitting the Sandbox request.
3. If your testing finds the bug fix works as expected and does not break other functionality:
   1. Sign off on the code through Git 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]."
      • Git setup and signoff instructions are available on the New Developers Group page.
   2. Add a signedoff tag to the LP bug.
   3. Remove yourself from the "Assigned To" field.
4. If you discover problems when testing, add a comment to the Launchpad bug.

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.

• August 17-21, 2020 (Feedback Fest)
• February 17 - 21, 2020 (Feedback Fest)
• September 9 - 13, 2019
• July 29 - August 2, 2019 (Feedback Fest)
• May 20 - 24, 2019
• March 4 - 8, 2019
• September 10 - 14, 2018
• May 21 - 25, 2018
• September 11 - 15, 2017
• July 17 - 21, 2017
• February 2 - March 3, 2017
• September 29, 2016
• June 2, 2016
• March 4, 2016
• June 10, 2015
• August 26, 2014