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, November the 11th.


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-699 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Nov/30/2020
  • RFC-699
    • Waiting from Gen3 to land, and then ping for additional comments
    • To update End Date at the end of November
  • RFC-695
    • End of November
Board Recommended RFCs
  • RFC-733 - Getting issue details... STATUS
  • Jonathan to open a ticket to implement it in rubinenv
Adopted but not implemented LDM RFCs (only document RFCs)


Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-739 - Getting issue details... STATUS Planned end: Nov/12/2020
  • RFC-737 - Getting issue details... STATUS Planned end: Nov/04/2020
  • RFC-727 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-739
    • KT to take care, not a CCB topic
  • RFC-737
    • Not a CCB topic
    • There is not clear convergence
    • It is RL choice to flag it, or extend the end date
  • RFC-727
    • KT to take
    • it is a T&S problem
    • Not a CCB topic

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-709 - Getting issue details... STATUS
    • Not sure if  DM-25908 - Getting issue details... STATUS  should be "Triggered By" instead of "Related"
  • RFC-723 - Getting issue details... STATUS
  • RFC-726 - Getting issue details... STATUS
  • RFC-709
    • It is waiting for LCR-2543
  • RFC-723
    • For Michelle Butler to comment and close
  • RFC-726
    • Yusra says that Crish is working on opening related tickets.

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

  • RFC-312 - Getting issue details... STATUS
  • Up to Simon to mark it as completed.
    • Yusra to ping Simon

RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-726 - Getting issue details... STATUS
  • RFC-736 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

  • RFC-703 - Getting issue details... STATUS
  • RFC-645 - Getting issue details... STATUS
  • RFC-736 - Getting issue details... STATUS
  • RFC-710 - Getting issue details... STATUS
  • RFC-620 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • Race condition identified in France. Should not ship known broken code. 
    • DM-27494
  • Also sconsUtils has been patched
    • DM-25914
  • Should we start with w46 given that Gen 3 is now available?

Action:

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-10326 - Getting issue details... STATUS
  2. DM-10351 - Getting issue details... STATUS
  3. DM-10377 - Getting issue details... STATUS
  4. DM-10325 - Getting issue details... STATUS
  5. DM-7787 - Getting issue details... STATUS
  6. DM-9048 - Getting issue details... STATUS
  7. DM-10339 - Getting issue details... STATUS
  8. DM-7479 - Getting issue details... STATUS
  9. DM-10446 - Getting issue details... STATUS
  10. DM-10445 - Getting issue details... STATUS

3911 unresolved issues (3920 on November the 4th)

  • 10351, 10326, 10351, 9048: Butler/task related; bounced to ARCH for dispatch.
  • 7479: Still relevant; assigned in current sprint


Open Actions

AOB



Next DM-CCB November 18th.To check if DM


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