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, April the 15th.


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-674 - Getting issue details... STATUS Planned end: Mar/17/2020
  • RFC-620
    • two documents to change
    • LCRs
  • RFC-
Board Recommended RFCs



Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-686 - Getting issue details... STATUS Planned end: Apr/15/2020
  • RFC-685 - Getting issue details... STATUS Planned end: Apr/10/2020
  • RFC-680 - Getting issue details... STATUS Planned end: Apr/01/2020
  • RFC-675 - Getting issue details... STATUS Planned end: Mar/06/2020
  • RFC-662 - Getting issue details... STATUS Planned end: Mar/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: Apr/30/2020

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-671 - Getting issue details... STATUS
  • RFC-684 - Getting issue details... STATUS
  • RFC-682 - Getting issue details... STATUS
  • RFC-681 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

  • RFC-683 - Getting issue details... STATUS
  • RFC-671 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • is RFC-686 blocking the release?
    • BVan should be able to look into it and do some work before the release
  • Other real work
    • DM-22578
    • DM-23374
  • the rest should be just trivial changes that can be done at any moment.

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity.

  1. DM-7960 - Getting issue details... STATUS
  2. DM-7958 - Getting issue details... STATUS
  3. DM-7997 - Getting issue details... STATUS
  4. DM-2996 - Getting issue details... STATUS
  5. DM-7934 - Getting issue details... STATUS
  6. DM-8089 - Getting issue details... STATUS
  7. DM-8098 - Getting issue details... STATUS
  8. DM-8075 - Getting issue details... STATUS
  9. DM-8170 - Getting issue details... STATUS
  10. DM-8219 - Getting issue details... STATUS

3984 unresolved issues (3999 on April the 1sr)

  • DM-7960 — obsolete in Gen3? If so, let's set to Won't Fix.
  • DM-7958 — as above.
  • DM-7997 — closing as Won't Fix.
  • DM-2996 — pure DAX issue; Fritz Mueller should comment.
  • DM-7934 — Won't Fix.
  • DM-8089 — Won't Fix.
  • DM-8098 — seems valid; low priority; comment on ticket.
  • DM-8075 — Tim (rightly) set as Won't Fix.
  • DM-8170 — good idea (sufficiently good that I thought we were doing this, but I was confused).
  • DM-8219 — Won't Fix, per discussion between Tim & Chris Waters.
Open Actions

AOB

Next DM-CCB April the 22nd


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 SwinbankDMCCB#64 (2020 - 09 - 16)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
John SwinbankDMCCB#51 (2020 - 05 - 27)