...
- Joseph Livesey - work to refresh and fix the
sawtooth-poetbuild is ongoing. - Kevin O'Donnell - long-running testing
- we need a solid description of the toolchain in use by the projects (docker, docker-compose, etc.)
- James Barry will scan the available documentation and media for mentions of the RAFT consensus to identify what needs to be touched when we deprecate/decommission it
- Mark Carroll - In order to get ahead of the types of questions we are getting on #sawtooth, Mark will review the documentation for the setups of the various "getting started" and identify the gaps
- Ryan Roberts - check the impact of migrating to prost on
sawtooth-sdk-rust - Ryan Roberts - check the impact of incorporating/enhancing sawtooth-sdk-with the tokio+TMQ version
- Ryan Roberts - get the tokio+TMQ SDK published somewhere so it can be poked at
...
- the principal issue driving the toolchain stuff is the confusion around docker-compose v1 and v2
- v1 and v2 have slightly different YAML parsing that shows up in awkward places
- container ids are different between v1 and v2
- Where possible/necessary we should update the YAML `version` fields in the various docker-compose files which either behave identically regardless of the binary version used OR have versions which demand one or the other docker-compose releases (either too high for v1 or too low for v2)
- Switching to docker-compose v2 everywhere will require a thorough going through of the various test setups in all the projects
Documentation
- ACTION: Mark Carroll to take over reviewing the docs for RAFT references
- ACTION: Mark Carroll continuing to review documentation
...