Skip to end of metadata
Go to start of metadata


Location

BrowserRoom SystemPhone Dial-in
https://bluejeans.com/761546516/
  1. Dial: 199.48.152.152 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)

Time

From 9.00 to 09.30 PT, Wednesday, July the 15th.


Attendees

Regrets

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-711 - Getting issue details... STATUS Planned end Jul/31/2020
  • RFC-710 - Getting issue details... STATUS Planned end Jul/28/2020
  • RFC-709 - Getting issue details... STATUS Planned end Jul/24/2020
  • RFC-708 - Getting issue details... STATUS Planned end Jul/24/2020
  • RFC-707 - Getting issue details... STATUS Planned end: Jul/10/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Jun/03/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Jul/31/2020
  • RFC-711
    • LDM-144, LDM-143, LDM-138, LDM-140
    • Keep them as LDM documents and add a paragraph that they are deprecated
  • RFC-710
    • DPDD
    • discussed together with RFC-709
  • RFC-709
    • LSE-61
    • DMS-REQ-0066 (never added) should be added to the DMSR, but this can be handled after the JDR
  • RFC-708
    • Documents to approve LDM-148, LDM-294, LDM-503, LDM-564, LDM-643
    • Not still ready for approval, CCB can take more time to review the documents
  • RFC-707
    • should go in the base environment
  • RFC-699
    • RGroundl commented on slack but not in the ticket
  • RFC-695
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-703 - Getting issue details... STATUS Planned end: Jun/30/2020
  • RFC-697 - Getting issue details... STATUS Planned end: June/12/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021

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-706 - Getting issue details... STATUS
  • RFC-704 - Getting issue details... STATUS
  • RFC-705 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

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


Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 21.0.0
    • Tentative schedule: November 2020

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity.

  1. DM-6055 - Getting issue details... STATUS
  2. DM-697 - Getting issue details... STATUS
  3. DM-1995 - Getting issue details... STATUS
  4. DM-9294 - Getting issue details... STATUS
  5. DM-5752 - Getting issue details... STATUS
  6. DM-7914 - Getting issue details... STATUS
  7. DM-1780 - Getting issue details... STATUS
  8. DM-9197 - Getting issue details... STATUS
  9. DM-4126 - Getting issue details... STATUS
  10. DM-9142 - Getting issue details... STATUS

3893 unresolved issues (3883 on July the 8th)

  • DM-6055: Still seems relevant to my naive eye; no idea if it has been addressed internally.
  • DM-1995: I think this is still true. It's a painful Jira Agile misfeature, but it seems unlikely that we will ever actually fix it. Suggest closing this as Won't Fix.
  • DM-9294: Tim has commented (and perhaps we can just remove the code and close this issue).
  • DM-7914: Added comment.
  • DM-1780: Added comment.
  • DM-4126: Nearly five years later, and this continues to be tiresome. Added comment.

DM-1995

  • discussion on Epics process improvement, this issue should be 'Won't Fix'
Open Actions

AOB

Kian-Tat Lim to propose a small change to the deprecation policy

Next DM-CCB July the 22ndNext week JDR, next DMCCB July 29th


Pending Flagged RFCs

Key Summary
Loading...
Refresh

Pending Proposed RFCs

Key Summary
Loading...
Refresh

Oldest issues

Key Summary
Loading...
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
John SwinbankDMCCB#64 (2020 - 09 - 16)
  • 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)