Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.05 to 09.35 PT, Wednesday, January the 8th.


Attendees

  • TBD

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

Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-638 - Getting issue details... STATUS Planned end: Jan/31/2020
  • RFC-648 - Getting issue details... STATUS Planned end: Dec/13/2019
  • RFC-650 - Getting issue details... STATUS Planned end: Dec/13/2019
  • RFC-651 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-652 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-653 - Getting issue details... STATUS Planned end: Jan/08/2020

Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

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

RFCs adopted since last CCB

(to review, no action required)

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

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

  • RFC-654 - 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:
  • Do we need a 20.0.1 patch?
    • so far no RFC open
      • see   DM-22703 - Getting issue details... STATUS  and related discussion

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-6025 - Getting issue details... STATUS  
  2. DM-5951 - Getting issue details... STATUS
  3. DM-6152 - Getting issue details... STATUS
  4. DM-6594 - Getting issue details... STATUS
  5. DM-6571 - Getting issue details... STATUS
  6. DM-6602 - Getting issue details... STATUS
  7. DM-5721 - Getting issue details... STATUS
  8. DM-5857 - Getting issue details... STATUS
  9. DM-5862 - Getting issue details... STATUS
  10. DM-5724 - Getting issue details... STATUS

3771 unresolved issues (3858 on December the 18th)


Open Actions

AOB

Next DM-CCB 



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 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)
  • Kian-Tat Lim to clarify the process to add new packages to the conda environment
Kian-Tat LimDMCCB#42 (2020 - 03 - 04)



  • No labels