Release 1.4 To Do
Here are things to do for the 1.4 release:
- (done) Documentation:
- (done) document snapshot phase (done)
- (done) document dynamic vars
- (done) document new tests
- try: echo "fuego-core/engine/tests/*" | xargs git-when-introduced.sh | sort -k 2 -V
- (done) document new quickstart (install.sh followed by start.sh)
- Do release testing
- default test plan:
- (done) test bbb
- (done) test docker
- (done) test min1
- (done) test ren1
- (done) test rpi3-2
- fuego test plan:
- (done) docker
- (done) fuego-test
- (done) ftc-test
- (done) min1
- (done) ren1
- (done) rpi3-2
- (done) triage test results:
- (done) fix priority bugs
- General:
- things to commit
- sync fix
- Functional.fuego_commit
- Functional.lava??
- more fujitsu tests?
- 'action' tests, to do: make_cache, make_report
- support remote test
- support squad back-end
- support interactive run-test (with interactive creation of board file)
- document log_this
- document snapshot function
- rename PLATFORM to TOOLCHAIN
- jobs now use ftc run-test
- ftc -b
- document how to use fserver
- how to use the existing fserver at fuegotest
- how to set up your own fserver
- add checkbox and replot to flot plots? (maybe not)
- change default port for Jenkins from 8080 to 8090
- support fuego release self-test (probably defer to 1.4 release)
- move fuego-core dir inside fuego
- create pre-built docker image
- more flake8 testing
- add check of parsing code to Functional.fuego_lint
- add backfire kernel module build
- parse LTP error descriptions
- process rst into html for testcases, and have it appear in Jenkins interface
- support board reboot (via BOARD_CONTROL) with another tool
- support lava, labgrid, r4d, or boruta (Pawel's) DUT control software?
- support board provisioning (via BOARD_CONTROL)
- remove or convert all chart_configs to proper files
- convert documentation to reStructureText
- create new user guide
- convert wiki architecture guide
- convert wiki developer reference materials