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, September the 30th.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescription

CCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-709 - Getting issue details... STATUS Planned end Jul/24/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-709:
    • Leanne will check today, probably move forward the due date.
  • RFC-699 due date in the future
  • RFC-695 due date in the future
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)
  • RFC-710 - Getting issue details... STATUS
    • waiting for LCR-2643 to finish
  • We may need to push the approval of LCR to move forward in RFC-710

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-727 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-726 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-723 - Getting issue details... STATUS Planned end: Aug/31/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • No CCB action required

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-710 - Getting issue details... STATUS (waiting for LCR-2643)
  • RFC-697 - Getting issue details... STATUS

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-703 - Getting issue details... STATUS
  • RFC-729 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

  • RFC-364 - Getting issue details... STATUS
  • RFC-718 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 21.0.0
    • DM-22815 - Getting issue details... STATUS  
    • Tentative schedule: November 2020
  • We need to start thinking at a concrete start/end date
  • Yusra to take care of the release note and clean the blockers (should be only deprecations)

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-9508 - Getting issue details... STATUS
  2. DM-9791 - Getting issue details... STATUS
  3. DM-9901 - Getting issue details... STATUS
  4. DM-9269 - Getting issue details... STATUS
  5. DM-9911 - Getting issue details... STATUS
  6. DM-9950 - Getting issue details... STATUS
  7. DM-9976 - Getting issue details... STATUS
  8. DM-9983 - Getting issue details... STATUS
  9. DM-10022 - Getting issue details... STATUS
  10. DM-10034 - Getting issue details... STATUS

3940 unresolved issues (3954 on September the 23rd)

9983: Per Tim, will close when formally moving to BG3

10034: Perhaps still relevant, though seemingly low priority since no action since 2017 until this ping...


  • Yusra AlSayyad to follow up on DM-9901 with J. Bosh and DM-9950 with J. Parejko


Open Actions


AOB



Next DM-CCB October 7th.


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
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)



  • No labels