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, July the 24th.


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-593 - Getting issue details... STATUS Planned end: Jul/31/2019

RFC-605 - Getting issue details... STATUS Planned end: Jun/26/2019

RFC-611 - Getting issue details... STATUS Planned end: Jul/15/2019

RFC-612 - Getting issue details... STATUS Planned end: Jul/15/2019

RFC-615 - Getting issue details... STATUS Planned end: Jul/18/2019

RFC-617 - Getting issue details... STATUS Planned end: Aug/02/2019

RFC-619 - Getting issue details... STATUS Planned end: Jul/19/2019

RFC-620 - Getting issue details... STATUS Planned end: Jul/24/2019

  • RFC-593: waiting for KT
    • due date has been moved to July 31
  • RFC-605: from the comments, it seems that Jim and Robert have converged. The proposal is not to block the RFC on a technote, but consider the technote as an implementation detail. 
    • Tim Jenness is the DMCCB requested to board recommend this RFC?
  • RFC-611: board recommended
  • RFC-612: board recommended
  • RFC-615: still no time to reviewing the costs... so better to withdraw the RFC
    • new cost model should be traced on a Jira issue. John Swinbankcommented that there should be 2 Jira issues, one for  the short term changes and one for the long term changes
      • Kian-Tat Lim to open an issue to review the cost model in the short term
      • Michelle Butler to find which issue is tracing the long term cost model activity
  • RFC-617: nothing to do
  • RFC-619: board recommended
  • RFC-620: it seems that this RFC will require much more time in order to be resolved, probably until the PCW, however, we need something for the review
    • John Swinbank says the proposed draft documents should be good for the review
    • Kian-Tat Lim had a look at them and it seems that what proposed is OK
      • Leanne Guy and SST to check the DPDD changes proposed in RFC-620
      • Tim Jenness to look at LSE-61 requirements changes by RFC-620
      • John Swinbank  to look at the proposed  LDM-151 changes in RFC-620
Board Recommended RFCs

None


Adopted but not implemented LDM RFCs (only document RFCs)

None


Proposed RFCs

(to review, do not require DMCCB approval)

RFC-616 - Getting issue details... STATUS Planned end: Jul/19/2019

RFC-585 - Getting issue details... STATUS Planned end: Jun/14/2019


Adopted RFCs without Triggering issues

(to create implementing DM issues)

None


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

RFC-599 - Getting issue details... STATUS


RFCs adopted since last CCB

(to review, no action required)

RFC-606 - Getting issue details... STATUS

RFC-618 - Getting issue details... STATUS

RFC-614 - Getting issue details... STATUS

RFC-613 - Getting issue details... STATUS


RFCs implemented since last CCB

(to review, no action required)

RFC-614 - Getting issue details... STATUS

RFC-613 - Getting issue details... STATUS

RFC-607 - Getting issue details... STATUS


Changes to the planned releases
  • Next Releases:
    • Accepted 18.1.0 as per 
    • RFC-618 - Getting issue details... STATUS
    • Jira issue   DM-20662 - Getting issue details... STATUS
  • Next Major release 19.0.0
    • Autumn 2019 
  • 18.1.0
    • backport done
    • first release candidate ready to go 

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-2416 - Getting issue details... STATUS
  2. DM-2272 - Getting issue details... STATUS
  3. DM-2180 - Getting issue details... STATUS
  4. DM-1823 - Getting issue details... STATUS
  5. DM-1778 - Getting issue details... STATUS
  6. DM-616 - Getting issue details... STATUS
  7. DM-690 - Getting issue details... STATUS
  8. DM-2313 - Getting issue details... STATUS
  9. DM-3781 - Getting issue details... STATUS
  10. DM-5268 - Getting issue details... STATUS

4019 unresolved issues (3957 on July the 17th)

From Fritz:

  • DM-2722, DM-616: May still be relevant (but may not because of config in Kubernetes world).  Fabrice needs to comment on these when he returns from holiday.
  • DM-2313: Still relevant, but a low priority optimization and hard to predict actual gain.

John Swinbank

  • DM-3781 is still valid, low priority.


Open Actions
All closed.
AOB

Next DM-CCB 
Next week July 31st


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#45 (2020 - 04 - 08)
Leanne GuyDMCCB#45 (2020 - 04 - 08)
  • Kian-Tat Lim to clarify the process to add new packages to the conda environment
Kian-Tat LimDMCCB#42 (2020 - 03 - 04)
Colin SlaterDMCCB#42 (2020 - 03 - 04)