Summary

Spec changes beyond a typo fix require a DRIVERS ticket. To ensure this information is widely known, we are adding it as a checklist item to the specifications repository.

Motivation

Spec changes beyond a typo fix require a DRIVERS ticket. Make it easier to garner context on a specifications change by enforcing a relevant DRIVERS ticket is made.

Who is the affected end user?

Any contributor to the mongodb/specification repository

How does this affect the end user?

How likely is it that this problem or use case will occur?

Anytime someone does not provide a DRIVERS ticket this problem will occur.

If the problem does occur, what are the consequences and how severe are they?

Leads to in a gap in information dissemination.

Is this issue urgent?

Non-urgent – still priority

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

No

Acceptance Criteria

PR enforcing our new guidelines (via manual ticking of a box in the checklist) should enforce this criteria. Any PR made beyond the point of the updated Pull Request Template will be subject to this new scrutiny.