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


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-717 - Getting issue details... STATUS Planned end: Jul/31/2020
  • RFC-713 - Getting issue details... STATUS Planned end: Jul/31/2020
  • RFC-711 - Getting issue details... STATUS Planned end Jul/31/2020
  • RFC-710 - Getting issue details... STATUS Planned end Jul/28/2020
  • RFC-709 - Getting issue details... STATUS Planned end Jul/24/2020
  • RFC-708 - Getting issue details... STATUS Planned end Jul/24/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Jun/03/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Jul/31/2020
  • RFC-717
    • Trivial change, formerly API racking changes
    • CCB approves it
  • RFC-713
    • Wil O'Mullane and Leanne Guy to check the changes and approve it. Just a catch up for a couple of DMTR already concluded in the past months
  • RFC-711
    • to discuss with KT next week
  • RFC-710 and RFC-709
    • It is not clear if the change to DMSR has been agreed
    • GPDF has agreed to resurrect DMS-REQ-0066
      • Tim Jenness  to check with GPDF: add DMS-REQ-66 to RFC-709 and rephrase it properly
  • RFC-708
    • Documents ready to be adopted, but better to wait for a few more updates to come int
  • RFC-699
    • DMCCB reach consensus, but a proposed text to go the devguide is required
      • John Swinbank respond on RFC-699: ask Eli Rykoff to propose a text to add tot he devguide
  • RFC-695
    • end date pushed to the end of august
Board Recommended RFCs

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-716 - Getting issue details... STATUS Planned end: Jul/29/2020
  • RFC-715 - Getting issue details... STATUS Planned end: Jul/23/2020
  • RFC-714 - Getting issue details... STATUS Planned end: Jul/22/2020
  • RFC-712 - Getting issue details... STATUS Planned end: Jul/31/2020
  • RFC-703 - Getting issue details... STATUS Planned end: Jun/30/2020
  • RFC-697 - Getting issue details... STATUS Planned end: June/11/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-715: CCB agreed to adopt it so that changes to the environment can be pushed forward
    • Flagged and board recommend
  • RFC-714: no problems from the CCB
  • RFC-712: just KT to take care
  • Others seem fine, do not need CCB action

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

RFCs implemented (or withdraw) since last CCB

(to review, no action required)



Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 21.0.0
    • Tentative schedule: November 2020

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity.

  1. DM-9389 - Getting issue details... STATUS
  2. DM-9390 - Getting issue details... STATUS
  3. DM-9401 - Getting issue details... STATUS
  4. DM-9405 - Getting issue details... STATUS
  5. DM-9408 - Getting issue details... STATUS
  6. DM-9409 - Getting issue details... STATUS
  7. DM-5223 - Getting issue details... STATUS
  8. DM-3011 - Getting issue details... STATUS
  9. DM-3123 - Getting issue details... STATUS
  10. DM-3132 - Getting issue details... STATUS

3887 unresolved issues (3893 on July the15th)

  • DM-9405: Tim has commented.
  • DM-9408: John has commented.
  • DM-9409: Tim has commented.
  • DM-5223: Tim has commented.
  • DM-3011: Reassigned to Architecture at Tim Jenness's suggestion.
  • DM-3123: John has commented.
  • DM-3132: John has commented.

Several of the “X has commented” tickets above cover tickets against Jenkins; those comments will remove them from the backlog, but hopefully Frossie Economou will take over and drive them.

Open Actions

AOB


Next DM-CCB August the 5th


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 SwinbankDMCCB#64 (2020 - 09 - 16)
  • 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)