dev:bug_squashing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:bug_squashing [2020/09/29 12:01] – [Previous Bug Squashing Days] tmccanna | dev:bug_squashing [2021/02/02 17:58] – [Testing Bug Fixes] tmccanna | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== 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. | ||
+ | * 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 ===== | ||
- | * **TBD** | + | * **Evergreen 3.7 Feedback Fest** |
+ | * February 8-12, 2021 | ||
+ | * **Evergreen Spring Bug Squashing Week** | ||
+ | * March 8-12, 2021 | ||
Line 44: | Line 64: | ||
Testing involves the following steps: | Testing involves the following steps: | ||
- | - Loading the code on a non-production server. | + | - Loading the code on a non-production server. |
- | - To avoid duplication of effort, add yourself to the " | + | - To avoid duplication of testing |
- 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]." |
dev/bug_squashing.txt · Last modified: 2024/09/09 14:16 by tmccanna