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, February the 12th.



DMCCB Meeting Goals

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • Planned end: Jan/15/2020
  • Planned end: Jan/24/2020
  • Planned end: Feb/14/2020
  • Planned end: Feb/14/2020
  • RFC-620 - waiting for Mario to upload final version. Leanne re-pinged him today
  • RFC-660
    • WOM - added note to this.
    • WOM - Is there more to do or do we release this for now ?
    • DMCCB agreed to change the status to board Recommend
  • RFC-666
    • Still to merge a PR
  • RFC-669
    • Acceptance tests for LSE-61
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • Planned end: Feb/12/2020
  • Planned end: Feb/03/2020
  • Planned end: Feb/26/2020
  • Planned end: Jan/08/2020
  • Planned end: Jan/22/2020
  • Planned end: Jan/22/2020
  • Planned end: Dec/13/2019
  • Planned end: Mar/31/2020
  • RFC-665: Leanne Guy will have a look today
  • RFC-662: on agenda for face 2 face
  • RFC-653: changes are already done in the code
  • RFC-638: is quite old
    • extended after the algorithm workshop, March 31st.

Adopted RFCs without Triggering issues

(to create implementing DM issues)

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

  • Still under investigation, if there is some wor to do.
    • An open ticket is related to it.

RFCs adopted since last CCB

(to review, no action required)

RFCs implemented (or withdraw) since last CCB

(to review, no action required)


  • Planned
  • Changes to the release schedule
  • Next planned major release 20.0.0
    • Planned for Spring 2020

    • Blocking issues open:
  • Do we need a patch or unscheduled release?
The community post on 20.0.0 should be just to clarify the timeline, and the release community post to be done more close to the start of the activity.

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity - 


3936 unresolved issues (3931 on February the 12th)

  • DM-7440: Still a desirable Qserv change, but low priority.
  • DM-7443: Good idea. Low priority.
  • DM-7148: Should be an Architecture ticket. Reassigned. Seems low priority.
  • DM-5461: A SQuaRE issue. Still seems relevant.
Open Actions


Next DM-CCB February the 19th(?)

Feb. 19th.

Pending Flagged RFCs

Pending Proposed RFCs
Oldest issues

Meeting outcome

Pending DMCCB Actions