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 7th.


Attendees

Regrets

  • none

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-709 - Getting issue details... STATUS Planned end Jul/24/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-709: still on Leanne
  • RFC-699 and 695, due end of the month, no action required now
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)
  • RFC-710 - Getting issue details... STATUS
    • waiting for LCR-2643 to finish
  • LCR-2643 approved now, work can move forward on RFC-710

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-731 - Getting issue details... STATUS Planned end: Oct/14/2020
  • RFC-730 - Getting issue details... STATUS Planned end: Oct/09/2020
  • RFC-727 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-726 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-723 - Getting issue details... STATUS Planned end: Aug/31/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-731
    • DMCCB seems OK
  • RFC-730 to Flag since it is an API change
    • Tim to escalate it and board recommending.
  • RFC-727 KT will ping again
  • Others do not require DMCCB attention

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-710 - Getting issue details... STATUS (waiting for LCR-2643)

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

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

RFCs adopted since the last DMCCB

(to review, no action required)



RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

  • RFC-722 - Getting issue details... STATUS
  • RFC-661 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 21.0.0
    • DM-22815 - Getting issue details... STATUS  
    • Tentative schedule: November 2020

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-10020 - Getting issue details... STATUS
  2. DM-10067 - Getting issue details... STATUS
  3. DM-10013 - Getting issue details... STATUS
  4. DM-10018 - Getting issue details... STATUS
  5. DM-10021 - Getting issue details... STATUS
  6. DM-10106 - Getting issue details... STATUS
  7. DM-339 - Getting issue details... STATUS
  8. DM-353 - Getting issue details... STATUS
  9. DM-361 - Getting issue details... STATUS
  10. DM-4039 - Getting issue details... STATUS

3938 unresolved issues (3940 on September the 30th)

  • Tim already reviewed the non  SciencePipelines issues
  • J.Bosh to review the SciencePipeliens ones
  • KT commented the 10020 is still valid but low priority
Open Actions
  • Action on John Swibanck to be moved to Yusra
AOB


  • Yusra announced that Jim Bosch will be the DMCCB representative for DRP
  • Tim commented that Python 3.8 is blocked on pybind11 with a non-trivial issue
Next DM-CCB October 14th.


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
  • Leanne Guy look at RFC-911, RFC-938, RFC-977 and RFC-970 since they may be completed already.  
24 Jan 2024Leanne GuyDMCCB#187 (2024 - 01 - 17)



  • No labels