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, May the 8th.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-581 - Getting issue details... STATUS Planned end: Mar/15/2019

Still pending
Board Recommended RFCs

None


Adopted but not implemented LDM RFCs (only document RFCs)

RFC-592 - Getting issue details... STATUS  Planned end: Feb/18/2019

Proposed RFCs

(to review, do not require DMCCB approval)

RFC-594 - Getting issue details... STATUS Planned end: May/03/2019

RFC-593 - Getting issue details... STATUS Planned end: May/01/2019

RFC-585 - Getting issue details... STATUS Planned end: Apr/22/2019


Adopted RFCs without Triggering issues

(to create implementing DM issues)

RFC-592 - Getting issue details... STATUS  Planned end: Feb/18/2019

Shall we have a triggered ticket? usualy don't.

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

None



RFCs adopted since last CCB

(to review, no action required)

RFC-595 - Getting issue details... STATUS

RFC-592 - Getting issue details... STATUS



RFCs implemented since last CCB

(to review, no action required)

None



Changes to the planned releases
  • 18.0 Release to be planned
    • start working end of May with due date end of June

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-3953 - Getting issue details... STATUS
  2. DM-2560 - Getting issue details... STATUS
  3. DM-2688 - Getting issue details... STATUS
  4. DM-2562 - Getting issue details... STATUS
  5. DM-2561 - Getting issue details... STATUS
  6. DM-2564 - Getting issue details... STATUS
  7. DM-2566 - Getting issue details... STATUS
  8. DM-2565 - Getting issue details... STATUS
  9. DM-4097 - Getting issue details... STATUS
  10. DM-4114 - Getting issue details... STATUS

4054 unresolved issues (4053 on May the 1st)

John Swinbank pre-meeting commentary:

  • Polled submitter & product owner for opinions on whether DM-3953 is still useful.
    • Conclusion: “yes, but at a low priority”.
  • DM-4097 fairly trivial; now in review.
  • DM-4114 closed as “invalid“.
  • Other tickets are outside my expertise, but I understand the Base & Net team does not currently use Jira for work tracking so can likely all be closed as “won't fix”.


Open Actions

AOB


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)

  • No labels