The project MUST have a version-controlled source repository that is publicly readable and has a URL.
The project's source repository MUST track what changes were made, who made the changes, and when the changes were made.
To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases.
It is SUGGESTED that common distributed version control software be used (e.g., git) for the project's source repository.
Unique version numbering
The project results MUST have a unique version identifier for each release intended to be used by users
It is SUGGESTED that the Semantic Versioning (SemVer) format be used for releases.
It is SUGGESTED that projects identify each release within their version control system. For example, it is SUGGESTED that those using git identify each release using git tags.
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". (URL required)
The release notes MUST identify every publicly known vulnerability with a CVE assignment or similar that is fixed in each new release, unless users typically cannot practically update the software themselves. If there are no release notes or there have been no publicly known vulnerabilities, choose "not applicable" (N/A).