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, September the 11th.


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-620 - Getting issue details... STATUS Planned end: Sep/09/2019

RFC-627 - Getting issue details... STATUS Planned end: Sep/10/2019


RFC-627:

  • The 2 obs pk’s that are dead.
  • Should we update the developer guide that jobs packages obsolete can be removed without RFCs
    • DMCCB#26 (2019 - 09 - 11) : it is not sure if we gain much about this procedure change
      • We can delegate to the pipelines PM or still, keep RFC
    • DMCCB#26 (2019 - 09 - 11): we do have a list of jobs pkg that we care about, to write in a list
      • The CCB has to keep an eye on this, therefore RFCs is the right approach
      • Or the CCB looks which are the good ones, and remove the others
  • After some discussion, DMCCB agreed to keep the actual procedure is fine.
  • Status changed to board recommend, no further actions on documentation required.

RFC-620

  • Still waiting for more inputs from Mario, end date pushed forward two weeks.


Board Recommended RFCs

None


Adopted but not implemented LDM RFCs (only document RFCs)

None


Proposed RFCs

(to review, do not require DMCCB approval)

RFC-624 - Getting issue details... STATUS Planned end: Aug/30/2019

RFC-628 - Getting issue details... STATUS Planned end: Sep/11/2019

No action required.

Adopted RFCs without Triggering issues

(to create implementing DM issues)

None


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

None


RFCs adopted since last CCB

(to review, no action required)

RFC-626 - Getting issue details... STATUS


RFCs implemented (or withdraw) since last CCB

(to review, no action required)

RFC-626 - Getting issue details... STATUS


Changes to the planned releases
  • Next Major release 19.0.0
    • Start it at the end of October and have it available at the end of November

    • DM-18119 - Getting issue details... STATUS


Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-5309 - Getting issue details... STATUS
  2. DM-1690 - Getting issue details... STATUS
  3. DM-2584 - Getting issue details... STATUS
  4. DM-2577 - Getting issue details... STATUS
  5. DM-2568 - Getting issue details... STATUS
  6. DM-2559 - Getting issue details... STATUS
  7. DM-2553 - Getting issue details... STATUS
  8. DM-1592 - Getting issue details... STATUS
  9. DM-4922 - Getting issue details... STATUS
  10. DM-5224 - Getting issue details... STATUS

3897 unresolved issues (3912 on September the 4th)

  • DM-5309 still seems relevant, albeit low priority.
  • Closed everything else before the meeting.
Open Actions

AOB

Next DM-CCB 


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)
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
 John SwinbankDMCCB#51 (2020 - 05 - 27)