-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Server Integration
-
Fully Compatible
-
v9.0, v8.3
-
SESIWhinery 2026-11-17, SESINickBeckenhome 2026-12-01
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The ask for each team:
- Insert the “Team Plan Template” into your team’s Infinite Burndown plans in its own tab
- Audit your list of tasks under your assigned_to_jira_team_<name> tag. See mongodb-mongo-master config: https://github.com/10gen/mongo/blob/master/etc/evergreen.yml, mongodb-mongo-master-nightly config: https://github.com/10gen/mongo/blob/master/etc/evergreen_nightly.yml, and task definition YAMLs: https://github.com/10gen/mongo/tree/master/etc/evergreen_yml_components/tasks (many task definitions are organized here)
- If your team owns tasks that feel like they should be assigned to a different team, propose that move via a PR and tag request review of the proposed team. See How should we handle large tasks that include tests owned by multiple teams?
- Create new tasks to isolate your best release-blocking tests
- Cross-check with BFs your team has resolved recently
- Then, apply the release_critical, infinite_release_critical, and non-deterministic tags to the tasks your team owns
- Backport these tags to v9.0, v8.3, v8.0, and v7.0, Server Release can provide the backport-exception
Please see Guidance for Teams - Server Task Classification for full details.