RFC-581: Kian-Tat Lim still need to do some cleaning
RFC-584:
Everybody agree with the actual environment upgrade, RFC set to "Board Recommend"
John Swinbank suggest to use the conda env as source of true
Tim Jenness conda environment need to be RFC before changes, but including (EUPS) 3rd party package, that now change quite a lot, this requires a quicker approach
Minor updates on some packages could be done without explicit CCB approval
Tim Jenness to announce the new conda env when available
DM-2369 and DM-2368 are valid issues but with a relatively low priority. 2368 is blocked by
DM-1014
-
Getting issue details...STATUS
, which requires action from Robert Lupton, but is unlikely to be a high priority for him & the SST.
DM-932 is a configuration system issue, which is nominally a DAX problem so I've assigned it appropriately. However, this issue seems low priority, and I do not expect them to work on it soon.
I closed all the other issues before the meeting.
Should the DMCCB not be considering the RFC _after_ the triggered tickets have been created, rather than before?
Having related issues is already a way to document the RFC proposal
After a short discussion, everybody agree that the board can ask for triggered issues to be open before approving the RFC
Tim Jenness to clarify in the Developer Guide that the DM-CCB can ask triggered issues can be opened on an RFC before approving it.