(2) Accomplish the feature(s) it was designed to accomplish. [In some cases, the feature itself may be dropped, and only bugfixes and/or optimizations landed instead.]
(3) Have merged/rebased all changes from `devel` into itself, and all conflicts resolved. ($ git pull --rebase origin devel)
(4) Have binaries and unnecessary cruft untracked and removed. (Keep an eye on .gitignore!)
(5) Compile and run properly - this should be confirmed via Harbormaster/Jenkins (if available).
(6) Be free of compiler errors and warnings (must compile with `-Wall -Wextra -Werror`).
(7) Be Valgrind pure (no memory leaks detected).
(8) Comply with Coding and Technical standards.
(9) Be free of linter errors. ($ arc lint --lintall)
(10) Be fully CSI commented.
(11) Have an up-to-date build script (generally CMake) if relevant.
(12) Contain relevant LIT tests, if the project is Goldilocks capable.
(13) Have a Test Plan, generally containing a list of Goldilocks tests the reviewer should run.
(14) Be reviewed, built, tested, and approved by at least one trusted reviewer (Staff or Trusted Contributor).
(15) Have up-to-date Sphinx documentation, which compiles with no warnings.
(16) Have all reviewer comments processed and marked "Done".