Parsec service 1.3.0 release

[gowthamsk-arm]

As we approach the next release of Parsec following an established process, Parsec will be released with v1.3.0, and we are aiming for Mid October.

Use this thread for discussions about the 1.3.0 release of the Parsec service, including:

• the timeline of the release
• the status of the work feeding into the release

Date of the Code Freeze (Tentative): 29th of September

Stages:

• Prior Code freeze

  • Notify the community about the code-freeze date, release date, and the release discussion on GitHub
  • Review PRs across Parsec repos
  • Merge approved PRs
  • Publish new versions of all managed crates and configure parsec service and tool to use them. See this guide.
  • Run cargo update for parsec service and tool
  • Manual review of the crates versions in parsec/cargo.toml and parsec-tool/cargo.toml
  • Check common dependency crates versions between the parsec service, parsec tool, and other crates
  • Make sure there are no critical threats in the system
  • Check the milestone list

• During code freeze

  • Issue release candidate tag 1.3.0-rc1
  • OpenSUSE packaging for the RC
  • Pull in the latest git dependencies in the crates to ensure the latest release would work.
  • Execute the normal e2e tests on hardware:
    • Raspberry Pi with mbed-crypto
    • Raspberry Pi with TPM
    • Raspberry Pi with Nitrokey HSM (pluggable USB)
    • N1SDP with Trusted Services
  • Execute fuzz testing for some time
  • Ask the Linux distributions packagers to try the tagged version
  • Ask the Parsec Yocto maintainers to try the tagged version
  • Ask any interested people to try the tagged version
  • Review the book and make sure all pages are up-to-date. In particular, make sure the Threat Model is up to date.
  • Make sure all the markdown pages (like the README) look good.
  • Make sure the rustdoc pages (on docs.rs) are looking good (before and after the release).
  • Update parsec book to change references from 1.2.0 to 1.3.0
  • If any bugs are reported, we fix bugs and then issue another release candidate,1.3.0-rcx
  • When All reported issues are addressed, make a GitHub release out of the last tag, which includes its changelog, and ask maintainers to release this version of Parsec.

• Release

  • Push the release tag 1.3.0 or the service and 0.7.0 for the parsec-tool
  • Publish the new quickstart bundle and update the quickstart guide with it

• Post-release

  • Close issues fixed in the release and the past milestone
  • Update, test, and upstream Yocto recipes for Parsec and parsec-tool
  • Make a new issue milestone for the next release
  • Update the Roadmap
  • Update the Parsec Release Process with what we learned.
  • If any bugs are reported, make new MINOR or PATCH tags (that would be {releave-version}.x for this release)
  • Update the Parsec Tool demo
  • Profit 🥂

[tgonzalezorlandoarm]

Release candidates for PARSEC:

• https://github.com/parallaxsecond/parsec/tree/1.3.0-rc1
• https://github.com/parallaxsecond/parsec/tree/1.3.0-rc2

Release candidates for PARSEC-TOOL:

• https://github.com/parallaxsecond/parsec-tool/tree/0.7.0-rc1

[gowthamsk-arm]

Parsec 1.3 recipes in meta-security master-next.
https://gitlab.com/akuster/meta-security/-/commit/77be5c4219c6733bea0ab7f2667b53f1c3371a80