https://docs.google.com/spreadsheets/d/1HQwIymXxp3cWOD_ZN0pVams3ZUyE2JEdJNgxuPtlw1M/edit?usp=sharing
Pierre -> drunc
Eric ->hsilibs
Diana -> timing
Eric -> integrations tests
Giovanna -> TP streams
Artur -> TP/TA/TC path
Gordon -> hermesmodules
Gordon/Giovanna -> dpdklibs
Ready for first release candidate on Friday 15th?
Eric: Been trying to get integrationtest working with generating hwmap/readout segment and integrating into pre-existing configuration. Blocked a little bit by not having a working reference configuration (appdal test-session/boot.json not working yesterday)
Diana: Working on timinglibs, testing
Giovanna: Tested FakeHSI integrated into the system, mixed with ta/tc stream into MLT. Artur worked with TC buffering. Naming of trigger apps based on what they are processing (TP, TA, TC).
Marco: Working on dashboards, will have to consult while running to make sure proper metrics are published.
Pierre: Changes in appdal, anyone tried drunc? Question about directory structure (test/config -> test/appdal/config). Might also have a PR in coredal
Artur: Fixes to trigger workflow, TAs already made, now TCs made and pushed into MLT. Recent PR for buffering TCs, and making them into Fragments and responds to DataRequests. Is there a way to create a graph of configurations? May be difficult with SmartDaqApps
Eric: Will need to ensure that we have v4-to-v5 documentation up-to-date (probably oksconfgen wiki with links to indico)
Release Candidate: Giovanna will make sure that test-session config works in localhost environment, Gordon will try running the CRP-4 config. Working configs are needed for release candidate.
After release? Need to review what the state of OKS is, and what we need to do to bring the rest of the consortium on-board. What feedback do we hope to collect from engineering release? What configuration changes should people try to make? How should feedback be reported?