When an iTC has completed writing a new cPP or updating an existing one, how should that iTC publish the documentation for release to the public?

Once all of the work on the cPP and its Supporting Document (SD) has been accepted by the iTC and is finalized, the iTC will need to follow the versioning information provided in the cPP Lifecycle Guide and refer to the procedure of publishing documents outlined in the Document Publishing Guide. Within the Document Publishing Guide, references are provided for tagging a repository with a new GitHub release number, merging a Pull Request (to update an existing cPP) into the master branch, and creating the documentation for the final release.

After the final documentation is created, the iTC should also have the documents posted on the Common Criteria Portal. This can be done directly by contacting NIAP (as they manage the Portal) and copying your scheme liaison/representative. Updates to the iTC community page on the Portal should also be provided.

Lastly, if the iTC is maintaining its own website (such as the github.io pages), the website should be updated and either directly host the files or point to their release in the GitHub repository.