Flagged RFCs
(To be approved by the DMCCB)
Planned end: Mar/15/2019
None
Planned end: Feb/18/2019
- Unknown User (gcomoretto)check with Eric Bellm status of RFC-592 and close activity
Proposed RFCs
(to review, do not require DMCCB approval)
Planned end: May/03/2019
Planned end: May/01/2019
Planned end: Apr/22/2019
- Unknown User (gcomoretto)to check if planned end of RFC-593 and RFC-585 need to be updated
Adopted RFCs without Triggering issues
(to create implementing DM issues)
Planned end: Feb/18/2019
Shall we have a triggered ticket? usualy don't.
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)
None
- 18.0 Release to be planned
- start working end of May with due date end of June
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Support to J. Swinbank monitoring activity
4054 unresolved issues (4053 on May the 1st)
John Swinbank pre-meeting commentary:
- Polled submitter & product owner for opinions on whether DM-3953 is still useful.
- Conclusion: “yes, but at a low priority”.
- DM-4097 fairly trivial; now in review.
- DM-4114 closed as “invalid“.
- Other tickets are outside my expertise, but I understand the Base & Net team does not currently use Jira for work tracking so can likely all be closed as “won't fix”.
- Tim Jennessto ping Jeff Kantor to update/close network tickets
