This page is synced automatically from the MariaDB/governance repository and may be periodically updated.
Response Times
| Event | Timings and deadlines |
|---|---|
| First response to a contribution | 7 calendar days |
| Contribution review | 30 working days, unless a different timeline was communicated explicitly |
| Maintainer not responding in a joint decision, before escalation | 10 working days. 1 working day if a critical security vulnerability is involved. |
| Maintainer inactivity before removal | 20 working days |
| Committer inactivity before removal | 1 calendar year |
| Orphaned subsystem review | 10 working days. Then quarterly to see if a change in the status is needed. |
| Time before merge for a pull request that needs a simple majority | At least 5 working days |
| Time before merge for a pull request that needs a supermajority | At least 10 working days |
This table summarizes the timing, response expectations, and deadlines defined in the Governance model to ensure project responsiveness and avoid deadlocks. Note that working days exclude vacations and holidays.