The Evergreen community can always use help from volunteers willing to test newly-contributed code.
These Evergreen bug fixes and code for new features 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 an Evergreen Sandbox.
- To avoid duplication of 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:
- 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]."
- 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 and remove yourself from the "Assigned To" field.