Skip to end of metadata
Go to start of metadata


BrowserRoom SystemPhone Dial-in
  1. Dial: or
  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, October the 23rd.



  • TBD

DMCCB Meeting Goals

      • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-620 - Getting issue details... STATUS Planned end: Oct/14/2019
  • RFC-620:  no news from Mario
    • updates to come in November, the due date to be updated.
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

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)

  • RFC-632 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)


  • Planned
  • Changes to the release schedule
  • Next planned major release 19.0.0
    • Start it at the end of October and have it available at the end of November
    • DM-18119 - Getting issue details... STATUS

    • Community post to be prepared this week. Next weekly could be the starting build for the release.
    • Blocking issues:
  • Gabriele Comoretto : are we confident to get those issues fixed this week?
  • Tim Jenness : are thos issues soft blocker or hard blocker
  • DM-21169: Simon Krughoff says the work could be finished and reviewed this week.
  • John Swinbank : The others can be pushed this week, or be done in a couple of weeks, it depends on the message from the CCB
  • Tim Jenness : DM-18036 - DM21169 are really blocker
  • John Swinbank : how hard is the timeline for starting the release now.
    • delaying the start of the release of two weeks should not be a problem, and we may be able to have it by the end of November.

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-5856 - Getting issue details... STATUS
  2. DM-5864 - Getting issue details... STATUS
  3. DM-935 - Getting issue details... STATUS
  4. DM-5603 - Getting issue details... STATUS
  5. DM-4715 - Getting issue details... STATUS
  6. DM-5777 - Getting issue details... STATUS
  7. DM-5779 - Getting issue details... STATUS
  8. DM-5814 - Getting issue details... STATUS
  9. DM-5851 - Getting issue details... STATUS
  10. DM-5801 - Getting issue details... STATUS

3867 unresolved issues (3897 on October the 16th)

Some issues assessed before the meeting. Science Pipelines issues will be reviewed shortly by John. 
Open Actions


T&S has a weekly meeting from 7 to 9 every week, should we move this 5 minutes later?

Next DM-CCB 
In 4 weeks time (November the 20th), if some RFC comes out, the discussion can go on in slack.

Pending Flagged RFCs

Key Summary

Pending Proposed RFCs

Key Summary

Oldest issues

Key Summary

Meeting outcome

Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
John SwinbankDMCCB#51 (2020 - 05 - 27)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)