2018-05-07 Core sprint 8 retrospective
Retrospective
What did we do well?
What should we have done better?
- Callenge of having a release in the middle of a sprint. Ideal would be to align sprint close to release.
- Idea for release activities to be separate from release completion
- DECISION park and revisit
- Run time integration
- CORE-384 - stand up a node and send tests to it
- Do we have this so that it's ready to run in Travis?
- It's in there, but the tests are not running correctly.
- Rholang team can help if there is some documentation to support
- Need to define where to put tests (internal or external)
- CORE-384 - stand up a node and send tests to it
- ISSUE Jeremy document how to run tests locally to support dev team
- ISSUE Jeremy set up infrastructure to run on a cron job external of Travis
- Cron job
- Cron cadence 6 hours
- Not generate green checks in GitHub (nice to have if possible)
- To test on
- Docker
- VMs
- Test (run in all environments)
- Drive REPL and EVAL and check output on server and client
- Need to create the REPL tests
- 100 times
- EVAL tests can use contents in the Rholang examples directory
- Need to create the REPL tests
- Bring the error back - remove max reader fix (last Henry fix for RNode v0.3.1 release) to test and observe error
- Drive REPL and EVAL and check output on server and client