Closed jcfreeman2 closed 7 months ago
To test: you want to see that daq-buildtools continues to function normally both for areas which use the traditional dunedaq
name for the common packages and for the new coredaq
name. A test nightly was cut yesterday which uses coredaq
, NFDT_DEV_240410_A9
.
One way to do this is, just check that the daq-buildtools documentation continues to work under both scenarios.
…elease is called either the traditional "dunedaq" or the new "coredaq"