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, November the 25th.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescription

CCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-737 - Getting issue details... STATUS Planned end: Nov/30/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Nov/30/2020
  • RFC-737
    • Discussion on the different inputs...
    • Tim to comment on it
Board Recommended RFCs
  • RFC-733 - Getting issue details... STATUS
    • Jonathan to open a ticket to implement it in rubinenv
  • Tim comment on RFC-733
Adopted but not implemented LDM RFCs (only document RFCs)


Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-742 - Getting issue details... STATUS Planned end: Nov/26/2020
  • RFC-741 - Getting issue details... STATUS Planned end: Nov/25/2020
  • RFC-727 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-742
    • the planned end should be next week, not a CCB issue
  • RFC-741
    • Discussion ongoing (in the PR)
    • Tim suggests the RFC should be flagged
      • the work has to be done in any way, but NCSA should sign off
    • Jim Bosh: all comments received so far are fine
    • Open point: NCSA has the bandwidth for it?
    • to Flag and Unknown User (mbutler) to have a look
  • RFC-727: Kt to have a look at it

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-709 - Getting issue details... STATUS
    • Waiting for LCR-2543
  • RFC-726 - Getting issue details... STATUS
    • From DMCCB71: Crish should be working on opening related tickets.

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

  • RFC-312 - Getting issue details... STATUS
    • From DMCC71: Yusra to ping Simon

RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-739 - Getting issue details... STATUS
  • RFC-735 - Getting issue details... STATUS
  • RFC-740 - Getting issue details... STATUS

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

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


Releases

  • Planned
  • Changes to the release schedule
  • Yusra working on Release Note
    • Tim agreed to add a bullet about the Gen3
    • To be clear that Gen2 will be removed after 22 release
  • Characterization Report still not available
  • Expected Release available end of next week (Dec 4th?)

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-10415 - Getting issue details... STATUS
  2. DM-10454 - Getting issue details... STATUS
  3. DM-10224 - Getting issue details... STATUS
  4. DM-10223 - Getting issue details... STATUS
  5. DM-10527 - Getting issue details... STATUS
  6. DM-10498 - Getting issue details... STATUS
  7. DM-10419 - Getting issue details... STATUS
  8. DM-9175 - Getting issue details... STATUS
  9. DM-9070 - Getting issue details... STATUS
  10. DM-8253 - Getting issue details... STATUS

3946 unresolved issues (3911 on November the 11th)

10527: still relevant; low priority

Tim add note to DM-10415

Yusra to add a note to DM-10454


Open Actions

AOB



Next DM-CCB December 2ndTim will be on holiday during December, KT will act as deputy.


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

Task report

Looking good, no incomplete tasks.