BrowserRoom SystemPhone Dial-in
  1. Dial: or bjn.vc
  2. Enter Meeting ID: 761546516 -or- use the pairing code

Dial-in numbers:

  • +1 408 740 7256
  • +1 888 240 2560 (US Toll-Free)
  • +1 408 317 9253 (Alternate Number)

Meeting ID: 761546516

(Back to the DMCCB page)


From 9.00 to 09.30 PT, Wednesday, April the 3rd.



DMCCB Meeting Goals

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • No action to take by the DMCCB

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-583: wait until the end of the week
  • No comments from DMCCB on RFC-585 and RFC-589

Adopted RFCs without Triggering issues

(to create implementing DM issues)


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')


RFCs adopted since last CCB

(to review, no action required)


RFCs implemented since last CCB

(to review, no action required)

Changes to the planned releases
  • 18.0 Release to be planned (no changes since last DMCCB)

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity

3927 unresolved issues (3827 on March. the 20th)

Pre-meeting homework:

  • DM-2876 is a reasonable, but very low priority, feature request.
  • DM-2994 is a low-impact (probable) bug in EUPS, with poor instructions to reproduce.
  • DM-3035, DM-864, DM-1723 are old DAX issues. I've asked Fritz Mueller to comment on whether they are still relevant.
  • DM-3190 is a docs ticket which we should act on.
  • Closed DM-708 as “Won't fix”.
  • DM-2944 just went into review (smile).
  • Marked DM-889 (an old epic full of complete stories) as “done”.
  • DM-3201 is a genuine issue, but has not been high enough priority to cause problems.
  • John Swinbank assess the issues that are still open, and a comment that the issues are still valid (DM-2876, DM-3190)

Pending Flagged RFCs

Pending Proposed RFCs
Oldest issues

Meeting outcome

Pending DMCCB Actions