Skip to main content

Maintainer Playbook

This page defines a practical review/merge process for OpenArca maintainers.

1. Triage incoming issues​

  • Label scope (backend, frontend, docs, security, ux).
  • Mark approachable issues as good first issue / help wanted.
  • Confirm acceptance criteria before implementation starts.

2. Review pull requests​

Prioritize in this order:

  1. security and permission model,
  2. behavioral regressions,
  3. test coverage and quality gates,
  4. readability and maintainability.

3. Review outcome standards​

  • Request changes if guardrails are weakened.
  • Ask for smaller split if PR scope is too broad.
  • Approve when scope, tests, and docs are consistent.

4. Merge readiness checklist​

  • CI/quality gates are green.
  • Manual smoke flow has no regressions.
  • Release notes/changelog updated if user-facing change.

5. Release discipline​

  • tag release candidates consistently,
  • keep Open Core roadmap visible,
  • avoid mixing Enterprise-only code into public repo.