Data Management
Space shortcuts
Page tree
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, May the20th.


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)



Board Recommended RFCs
  • RFC-689 - Getting issue details... STATUS
    • see below 19.0.1 discussion

Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-696 - Getting issue details... STATUS Planned end: May/26/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Jul31/2020
  • RFC-685 - Getting issue details... STATUS Planned end: Apr/10/2020
  • RFC-680 - Getting issue details... STATUS Planned end: Apr/01/2020
  • RFC-652 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-651 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2020
  • RFC-696 should be flagged probably
  • RFC-685 to be addressed by KT
  • RFC-680 should be fine
  • RFC-652 and RFC-651, GPDF is taking care
  • RFC-638 resurrected, discussion ongoing.

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-693 - Getting issue details... STATUS
  • RFC-692 - Getting issue details... STATUS
  • RFC-694 - Getting issue details... STATUS
  • RFC-688 - Getting issue details... STATUS
  • RFC-674 - Getting issue details... STATUS

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

  • RFC-682 - Getting issue details... STATUS
  • RFC-679 - Getting issue details... STATUS
  • RFC-690 - Getting issue details... STATUS
  • RFC-684 - Getting issue details... STATUS
  • RFC-674 - Getting issue details... STATUS
  • RFC-675 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • John Swinbankadded DM-24618 as a blocker on 20.0.0 before the meeting, by request of several members of the Pipelines team.
    • also DM-25000 may be a blocker
    • the environment should be reasonable stable
    • Kian-Tat Lim we may need to change something in the environment for the T&S, but this will require time
    • Next weekly 21 should be good to go
    • The warning issue should be solved also
  • 19.0.1:
    • RFC to withdraw
    • the check with Leanne Guy that this is fine
    • Future infrastructural changes may still generate problems to the ability to do patch releases
    • The Jenkins infrastructure, in the long term, needs to be simplified and made more robust

Monitor Jira issues status:

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

Pending to review from previous CCB:

  1. DM-8305 - Getting issue details... STATUS
  2. DM-6877 - Getting issue details... STATUS
  3. DM-6599 - Getting issue details... STATUS
  4. DM-5852 - Getting issue details... STATUS
  5. DM-5853 - Getting issue details... STATUS

Support to J. Swinbank monitoring activity.

  1. DM-8572 - Getting issue details... STATUS
  2. DM-8435 - Getting issue details... STATUS
  3. DM-8664 - Getting issue details... STATUS
  4. DM-4096 - Getting issue details... STATUS
  5. DM-8722 - Getting issue details... STATUS
  6. DM-8744 - Getting issue details... STATUS
  7. DM-8745 - Getting issue details... STATUS
  8. DM-8746 - Getting issue details... STATUS
  9. DM-8747 - Getting issue details... STATUS
  10. DM-8748 - Getting issue details... STATUS

3957 unresolved issues (3965 on May the 6th)

  • DM-8305: Tim Jenness added a comment. Clearly not urgent; maybe not necessary.
  • DM-6599: Ditto.
  • DM-5852: Needs attention from Frossie Economou.
  • DM-5853: Needs attention from Frossie Economou.
  • All other tickets closed.
  • Actions: 
Open Actions

AOB

Next DM-CCB May the 27th


Pending Flagged RFCs

Key Summary
Refresh

Pending Proposed RFCs

Key Summary
Refresh

Oldest issues

Key Summary
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
 Tim JennessDMCCB#51 (2020 - 05 - 27)