Pre-release check list

[steven-bellock]

This thread lists all the activities that should be performed before releasing a new version of libspdm / spdm-emu / spdm-dump. It is a template and for each instance of a release we'll create an issue in https://github.com/DMTF/libspdm/issues.

High Priority

• Ensure that all relevant files have the DMTF copyright and license header and that the copyright date is correct.
• Ensure that the documentation is accurate, up to date, and in sync with the code and that new features in the release have been documented. This includes updating / removing URLs.
• Ensure that the change log is correct.
• Ensure that all three repositories are in sync with one another.

Medium Priority

• Run extended fuzz testing and formal verification on the candidate release. This includes increasing test duration as well as increasing the number of configurations tested.
• Evaluate open issues and enhancements and either defer them to the next release or bring them to the current release.

Low Priority

• ???

[steven-bellock]

@jyao1 Can we add extended fuzz testing to Github Actions? According to https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration Github allows up to six hours per test.