Flagged RFCs
(To be approved by the DMCCB)
Proposed RFCs
(to review, do not require DMCCB approval)
Adopted RFCs without Triggering issues
(to create implementing DM issues)
None
Adopted RFCs with all triggered work COMPLETED
(to set status as 'IMPLEMENTED')
None
RFCs adopted since last CCB
(to review, no action required)
RFCs implemented since last CCB
(to review, no action required)
- 18.0 Release to be planned
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Support to J. Swinbank monitoring activity
3827 unresolved issues (3819 on March. the 20th)
- Pre-meeting comments from John Swinbank :
- DM-2369 and DM-2368 are valid issues but with a relatively low priority. 2368 is blocked by DM-1014, 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?
