Let us know how we are doing

Take the DCI Working Group's new survey!

Page tree
Skip to end of metadata
Go to start of metadata


Minutes Link

Overview of Proposal

Hyperledger Explorer team is seeking to have a major release v1.0.0 of the project, a Web tool for Hyperledger Fabric blockchain, below is the Criteria for First Major Release.

RequirementHyperledger Explorer Community Response
1Project has reached active status (the processes and community are mature)HL Explorer needs a major release before graduating to active status
2The release features substantially fulfill the project's charterYes
3The 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-rc2 published on Dec 10th 2019

  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
4The 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

HLExplorer CII Best Practices

  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 notesdone, by automatic scan

      ii. crypto code included in the release has been audited for crypto export complianceN/A

  c. A license scan was completed and all issues were resolved, including receiving an exception from the legal committee.

Assigned   BE-723 - Getting issue details... STATUS

  d. Changelog of all commits is generated and published.done

  e.  Release notes generated and published.done

Formal Proposal(s)

Hyperledger Explorer major release v1.0.0

Action Items

  • Type your task here, using "@" to assign to a user and "//" to select a due date

Reviewed By


  1. This is an interesting test case for the TSC, as it is the first project to ask for a 1.0 that doesn't have a security component.

    1. I guess my main question is whether we should have a "Hyperledger XXX" project in 1.0 that only applies to one core DLT.  It might imply to the community that it is "finished" and thus will not support other projects (which might be fine, but in that case, Fabric Explorer might be a better name).  What do people think about this?

  2. Hart Montgomery Thank you for your comment, HLExplorer was designed to implement other types of blockchains, not only HL Fabric, of course it would require to implement it.

  3. I know I unfortunately missed the past two TSC meetings ... but do we really need to tie "version" to "status"?  I guess there are the benefits / requirements that come along with major releases (security scans, etc).

  4. I realize that this decision was somewhat buried into our wiki and hard to find but the TSC has defined a set of criteria one needs to fulfill for a first major release.

    To make it easier I've added it (along with others) to the decision log and the details can now be found here: Criteria for First Major Release

  5. Arnaud J Le Hors Thank you,  we will align the project accordingly to the Criteria for First Major Release .

  6. Note from the Project Lifecycle, the project does not need to be Active to request First Major Release. The question in my mind is whether the result of reaching First Major Release is different for a tool than it is for a DLT?

    1. The log reflects that we changed this recently:

      Issue 2: What are the criteria for a "First Major Release"?

      Again, this reflects some of the major issues with our documentation that I've attempted to address in emails.

      1. Thanks, Hart. I missed that.

  7. Tracy Kuhrt Tracy can you assign license scan to someone? Thank you

    1. Not sure who on Silona Bonewald's team is doing license scanning now. 

      1. David Huseby  works with Steve Winslow

        1. Ry Jones  I have created a Jira for the scan, can i assign it to David Huseby ?

          Thank you Ry.

          1. sure, I assigned it to him

          2. I just added the most recent results to the jira. If those results are new enough to capture the most recent changes in explorer, I expect the next one to happen in January and that one will.

  8. Unable to attend tomorrow TSC meeting, someone may attend, please post any questions/comment regarding HLExplorer.