Passing criterion release_notes (MUST; group Change Control, Release notes). Criterion text: The project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the "git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ continuous delivery MAY select "N/A".
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.