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, February the 19th.


Attendees

Regrets

  • TBD

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-620
    • no news
  • RFC-666
    • There are still some comments to address.
  • RFC-671
    • spreadsheet updated to reflect reality
    • Wil O'Mullane will review and upload in Docushare
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-670 - Getting issue details... STATUS Planned end: Feb/19/2020
  • RFC-663 - Getting issue details... STATUS Planned end: Feb/21/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-648 - Getting issue details... STATUS Planned end: Dec/13/2019
  • RFC-638 - Getting issue details... STATUS Planned end: Mar/31/2020

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-665 - Getting issue details... STATUS
There is a triggering issue now.

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since last CCB

(to review, no action required)

  • RFC-653 - Getting issue details... STATUS
  • RFC-665 - Getting issue details... STATUS
  • RFC-660 - Getting issue details... STATUS
  • RFC-669 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)



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:

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity - 

  1. DM-7584 - Getting issue details... STATUS  
  2. DM-7583 - Getting issue details... STATUS
  3. DM-7616 - Getting issue details... STATUS
  4. DM-5001 - Getting issue details... STATUS
  5. DM-7493 - Getting issue details... STATUS
  6. DM-7688 - Getting issue details... STATUS
  7. DM-7699 - Getting issue details... STATUS
  8. DM-7718 - Getting issue details... STATUS
  9. DM-7686 - Getting issue details... STATUS
  10. DM-7703 - Getting issue details... STATUS

3932 unresolved issues (3936 on February the 19th)

Everything except DM-7718 is closed as of 2020-02-18; that one is currently running through Jenkins.
Open Actions

AOB


Next DM-CCB Skip February the 26th (DMLT), on March the 4th(?)

March the 4th.


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
Gabriele ComorettoDMCCB#45 (2020 - 04 - 08)
Leanne GuyDMCCB#45 (2020 - 04 - 08)
Colin SlaterDMCCB#42 (2020 - 03 - 04)
  • Kian-Tat Lim to clarify the process to add new packages to the conda environment
Kian-Tat LimDMCCB#42 (2020 - 03 - 04)