Hyperledger Explorer Promoted release v1.0.0
Status | WITHDRAWN |
Blocking | |
Outcome | Withdrawn by author |
Minutes Link |
Overview of Proposal
Hyperledger Explorer team is seeking to have a promoted release v1.0.0 of the project, a Web tool for Hyperledger Fabric blockchain.
| Requirement | Hyperledger Explorer Community Response |
|---|---|---|
1 | Project has reached active status (the processes and community are mature) | HL Explorer needs a promoted release before graduating to active status |
2 | The release features substantially fulfil the project's charter | Yes |
3 | The release satisfies criteria defined by the project itself. All projects should meet some internally defined non-functional release criteria (bug counts, performance, etc.) |
|
| a. Test coverage (unit and functional/integration) is sufficient to have confidence that the release supports the non-functional criteria | Test coverage meets criteria |
| b. Maintainers have reviewed all remaining open bugs and agree on severity/priority | No high priority bugs |
| c. Zero high or highest priority bugs remain open | zero high priority bugs |
| d. The preceding release candidate has been published for a minimum period of time of 2 weeks | v1.0.0 published on Apr 26th 2020 |
| e. The release should not require users/operators to compile code to operate the base project on supported platforms | Minor configuration required, build scripts provided and available repo Hyperledger Explorer docker repository. |
| f. The documentation is sufficient to ensure that users/operators have clear guidance on how to get started and how to configure and operate. | Instruction provided in Run Hyperledger Explorer Using Docker |
4 | The project has met all technical criteria for the release. |
|
| a. The project has met all the criteria for CII Best Practices Badge Best Practices Badge | |
| b. A security audit provided by Hyperledger was completed |
|
| i. no bugs that affect security of the system remain open unless they have mitigating workarounds published in release notes | done, by automatic scan |
| ii. crypto code included in the release has been audited for crypto export compliance | N/A |
| c. A license scan was completed and all issues were resolved, including receiving an exception from the legal committee. | done |
| d. Change log of all commits is generated and published. | done |
| e. Release notes generated and published. | done |
|
|
|
Formal Proposal(s)
Hyperledger Explorer promoted release v1.0.0
Action Items
Reviewed By