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, March the 4th.


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-620 - Getting issue details... STATUS Planned end: Jan/15/2020
  • RFC-666 - Getting issue details... STATUS Planned end: Feb/14/2020
  • RFC-671 - Getting issue details... STATUS Planned end: Mar/02/2020
  • RFC-674 - Getting issue details... STATUS Planned end: Mar/03/2020
  • RFC-620: end date pushed forward to March 31st
  • RFC-666: KT is fine with it, the board recommended.
  • RFC-671: requires more clarification
  • RFC-674: WOM commented it is fine.
    • Leanne Guy to review LDM-732 (RFC-674)  
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-675 - Getting issue details... STATUS Planned end: Mar/06/2020
  • RFC-673 - Getting issue details... STATUS Planned end: Mar/10/2020
  • RFC-662 - Getting issue details... STATUS Planned end: Feb/26/2020
  • RFC-652 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-651 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Mar/31/2020
  • RFC-675: TJ asks if should CCB care about adding packages?
    • KT agrees that DMCCB should
    • DMCCB may limit for the moment to monitor, and eventually, take action if those additions become too frequent
    • GCM: Should we figure out how to manage multiple environments, one on top of the others
    • CS: it could be added first to the shared stack and then moved to the conda env.
      • Kian-Tat Lim to clarify the process to add new packages to the conda environment (DM-25219)
  • RFC-673: it may require an LCR, WOM to decide.
  • RFC-662: actions from DMLT to address some implementation aspects

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-670 - Getting issue details... STATUS
  • RFC-672 - Getting issue details... STATUS
  • RFC-663 - Getting issue details... STATUS
  • RFC-648 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

  • RFC-660 - Getting issue details... STATUS
  • RFC-664 - Getting issue details... STATUS
  • RFC-665 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • Next planned major release 20.0.0
    • Planned for Spring 2020
      DM-20564 - Getting issue details... STATUS

    • Blocking issues open:
A few blockers are now in progress and in review

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity - 

  1. DM-7763 - Getting issue details... STATUS  
  2. DM-7772 - Getting issue details... STATUS
  3. DM-7773 - Getting issue details... STATUS
  4. DM-7786 - Getting issue details... STATUS
  5. DM-7838 - Getting issue details... STATUS
  6. DM-7847 - Getting issue details... STATUS
  7. DM-6662 - Getting issue details... STATUS
  8. DM-5872 - Getting issue details... STATUS
  9. DM-7323 - Getting issue details... STATUS
  10. DM-7849 - Getting issue details... STATUS

3858 unresolved issues (3932 on February the 19th)

  • DM-7763 — Won't Fix.
  • DM-7772 — Still a minor issue; low priority.
  • DM-7773 — Still a minor issue; low priority
  • DM-7786 — Will be reevaluated during upcoming KPM-50 testing and closed or updated that that time.
  • DM-7838 — Work has been carried out on other tickets; Invalid.
  • DM-7847 — Low priority feature request.
  • DM-6662 — Won't Fix.
  • DM-5872 — Low priority feature request.
  • DM-7323 — Invalid.
  • DM-7849 — Low priority feature request.
Open Actions

AOB


Next DM-CCB March the 11th

March  11th


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
Kian-Tat LimDMCCB#60 (2020 - 08 - 05)
Gabriele ComorettoDMCCB#60 (2020 - 08 - 05)
  • 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)