Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
dev:bug_squashing [2020/09/22 09:33] – [Overview] tmccanna | dev:bug_squashing [2021/02/04 16:04] – [Overview] tmccanna |
---|
====== Evergreen Bug Squashing Week ====== | ====== Evergreen Bug Squashing Week ====== |
| |
| ===== Introduction ===== |
| |
| The goal of **Bug Squashing Week** is for contributors and volunteers to commit time throughout the week to the following activities: |
| * Fixing bugs; |
| * Testing bug fixes that have pullrequest tags; |
| * General bug wrangling activities (confirming bugs, marking duplicates, etc.); |
| * Pushing bug fixes into Evergreen (for core committers). |
| |
| **Feedback Fest** is a week(ish)-long event with the goal to provide feedback on each and every outstanding pull request. Feedback can take many forms, including: |
| * rebasing older pull request branches against the current master |
| * commenting on the bug and the proposed patches |
| * deciding if the bug no longer applies |
| * testing and signing off on the patches |
| * writing automated test cases for pull requests that need them |
| * writing human test plans |
| * writing release note entries |
| |
===== Upcoming Bug Squashing Weeks ===== | ===== Upcoming Bug Squashing Weeks ===== |
| |
* **September 21-25: Bug Squashing Week** | * **Evergreen 3.7 Feedback Fest** |
| * February 8-12, 2021 |
| * **Evergreen Spring Bug Squashing Week** |
| * March 8-12, 2021 |
| |
| |
* Testing [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on| bugs with the "New" status]] that other people have reported in order to confirm them. | * Testing [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on| bugs with the "New" status]] that other people have reported in order to confirm them. |
* Testing [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=-pullrequest&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on|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 [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=-pullrequest&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on|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 [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&field.importance%3Alist=LOW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=pullrequest+-signedoff&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on|pullrequest tag]] to be sure that they work (see Testing Bugs section below). | * Testing bug fixes that have the [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=pullrequest%20-signedoff&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search&orderby=id&start=0|pullrequest tag]] to be sure that they work (see Testing Bugs section below). |
* Providing additional feedback on bugs that have not yet been fixed. | * Providing additional feedback on bugs that have not yet been fixed. |
* Adding tags to bugs - please see the [[dev:lp_tags|list of current official tags]] (as of Summer 2020). | * Adding tags to bugs - please see the [[dev:lp_tags|list of current official tags]] (as of Summer 2020). |
Testing involves the following steps: | 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 [[https://goo.gl/forms/nCrexnSJNrufszHm1|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. | - Loading the code on a non-production server. The bug squashing coordinator will also arrange to have test servers loaded with proposed bug fixes and new features. |
- To avoid duplication of effort, add yourself to the "Assigned To" field in the Launchpad bug after submitting the Sandbox request. | - To avoid duplication of testing 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: | - If your testing finds the bug fix works as expected and does not break other functionality: |
- 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]." | - 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]." |
| |
===== Previous Bug Squashing Days ===== | ===== Previous Bug Squashing Days ===== |
| |
| * [[dev:bug_squashing:2020-09|September 21-25, 2020]] |
* [[dev:feedback_fest_2020-08|August 17-21, 2020 (Feedback Fest)]] | * [[dev:feedback_fest_2020-08|August 17-21, 2020 (Feedback Fest)]] |
* [[dev:feedback_fest_2020-02|February 17 - 21, 2020 (Feedback Fest)]] | * [[dev:feedback_fest_2020-02|February 17 - 21, 2020 (Feedback Fest)]] |