...
Proposed/Draft Resolution 2:
...
- Have reached active status (the processes and community are mature)
- Implies release has met all the criteria for CII Best Practices Badge Best Practices Badge,
- Completed a security audit provided by Hyperledger
- no bugs that affect security of the system remain open unless they have mitigating workarounds published in release notes
- crypto code included in the release has been audited for crypto export compliance
- Completed a license scan
- The release features substantially fulfill the project's charter
- The release satisfies criteria defined by the project itself. All projects should meet some internally defined non-functional release criteria (bug counts, performance, etc.)
- adequate test coverage (unit and functional/integration) to have confidence that the release supports the non-functional criteria
- maintainers have reviewed all remaining open bugs and agree on severity/priority
- zero high or highest priority bugs remain open
- the preceding release candidate will have been published for a minimum period of time
- release will not require users/operators to compile code to operate the base project
- documentation sufficient to ensure that users/operators have clear guidance on how to get started and how to configure and operate. The operational aspects need to be correct and independently user tested
- signed release code (not sha1, which is what git currently uses as that is no longer secure), published images (DTR) and binaries,
- release notes