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, July the 17th.



DMCCB Meeting Goals

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

Planned end: Jun/14/2019

Planned end: Jun/26/2019

Planned end: Jul/15/2019

Planned end: Jul/15/2019

Planned end: Jul/12/2019

Planned end: Jul/13/2019

Planned end: Jul/18/2019

Planned end: Aug/02/2019

Planned end: Jul/23/2019

Planned end: Jul/19/2019

  • RFC-593: end date moved to July 31
  • RFC-605: seems fine, but RLupton would like this to be fixed somewhere else
    • Technote could be written but no time for it
    • To keep on hold: to move the end date one week
  • RFC-617: for the CCB point of view it is fine. Add a comment.
  • RFC-611: 
    • section 3 to be renamed Verification Control
    • Ready to be adopted
  • RFC-612:
  • RFC-613: LDM-152
    • so far no problems from the DMCCB, the 
  • RFC-614: LDM-148
    • new product tree and some minor changes
    • OK
  • RFC-615: LDM-144
    • Kian-Tat Lim has a look and changes seems reasonable, some concerns about costs increasing
    • Michelle Butler the model used to do this estimation is quite old, and it should be reviewed
    • Kian-Tat Lim suggests not to modify the baseline, but to submit the document to the review as a draft.
    • DM-CCB decided not to Board Recommend the RFC and review the document trying to reduce the costs.
  • RFC-619: LDM-672
Board Recommended RFCs

Planned end: Jul/01/2019

Adopted but not implemented LDM RFCs (only document RFCs)


Proposed RFCs

(to review, do not require DMCCB approval)

Planned end: Jul/19/2019

Planned end: Jun/14/2019

  • no comments.

Adopted RFCs without Triggering issues

(to create implementing DM issues)

RFC-607 has a triggered ticket as of shortly after this page being published. (Thanks, Tim Jenness )

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.0 Release status
    • Release completed.
  • Next Releases:
    • proposed 18.1.0 as per RFC-618
  • RFC-618: DMCCB is fine
    • Gabriele Comorettoto open a Jira issue for the 18.1.0 release and comment on the RFC-618, release to be available in 2 weeks

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

3957 unresolved issues (3937 on July the 10th)

  • DM-2918 still valid. Bumped ticket.
  • DM-5184 now in review done.
Open Actions

  • Gabriele Comorettoto open a Jira issue to update the DevGuida with John's proposed deprecation procedure in DM-20119
Next DM-CCB 
July the 24

Pending Flagged RFCs

Pending Proposed RFCs
Oldest issues

Meeting outcome

Pending DMCCB Actions