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 5 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.00 to 09.30 PT, Wednesday, October the 2nd.


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

Board Recommended RFCs



Adopted but not implemented LDM RFCs (only document RFCs)



Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-632 - Getting issue details... STATUS
  • RFC-634 - Getting issue details... STATUS
  • RFC-633 - Getting issue details... STATUS
  • RFC-635 - Getting issue details... STATUS


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-630 - Getting issue details... STATUS


RFCs implemented (or withdraw) since last CCB

(to review, no action required)

RFC-631 - Getting issue details... STATUS



Changes to the planned releases
  • Next Major release 19.0.0
    • Start it at the end of October and have it available at the end of November
    • DM-18119 - Getting issue details... STATUS


Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-5549 - Getting issue details... STATUS
  2. DM-5557 - Getting issue details... STATUS
  3. DM-5526 - Getting issue details... STATUS
  4. DM-5589 - Getting issue details... STATUS
  5. DM-5605 - Getting issue details... STATUS
  6. DM-424 - Getting issue details... STATUS
  7. DM-4380 - Getting issue details... STATUS
  8. DM-5354 - Getting issue details... STATUS
  9. DM-4725 - Getting issue details... STATUS
  10. DM-4262 - Getting issue details... STATUS

xxxx unresolved issues (xxxx on September the 25th)


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






  • No labels