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, February the 6th.

Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-571 - Getting issue details... STATUS

RFC-572 - Getting issue details... STATUS

  • RFC-571 People from outside DM starts commenting the RFC. Need to be agreed at a System Engineering level. LCR need to be opened to find an agreement at the project level.
    • However DM, Robert and Simon to agree to the approach first
  • RFC-572 Update LDM-294: RFC branch need to be rebased and PR created.
    • Tim Jenness: the doc system is not helpful when using protected branches. The out of draft version can't be merged. The proposed process is to have the last commit to removing draft, get the doc for DocuShare and tag, do a revert, going back to draft version, and then merge. So all tags will visible from the master.
    • Tim Jenness to update dev guide with the proposed procedure for merging an approved RFC ticket. DM-17861 - Getting issue details... STATUS  

Proposed RFCs

(to review, do not require DMCCB approval)

RFC-570 - Getting issue details... STATUS

RFC-541 - Getting issue details... STATUS

RFC-533 - Getting issue details... STATUS

  • RFC-570, no deprecation cycle required
  • RFC-541,
  • RFC-533 waiting for an implementation ticket, comment added during the telecom.

Adopted RFCs without Triggering issues

(to create implementing DM issues)

None


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

  • RFC-285 - Getting issue details... STATUS
  • RFC-551 - Getting issue details... STATUS (comments added after discussion on previous DMCCB)


RFCs adopted since last CCB

(to review, no action required)

RFC-551 - Getting issue details... STATUS

RFC-563 - Getting issue details... STATUS

RFC-569 - Getting issue details... STATUS

RFC-552 - Getting issue details... STATUS


RFCs implemented since last CCB

(to review, no action required)

RFC-557 - Getting issue details... STATUS

RFC-538 - Getting issue details... STATUS

RFC-568 - Getting issue details... STATUS

RFC-449 - Getting issue details... STATUS

RFC-134 - Getting issue details... STATUS

RFC-550 - Getting issue details... STATUS

RFC-516 - Getting issue details... STATUS

RFC-561 - Getting issue details... STATUS



Changes to the planned releases
  • 17.0 planned for the end of 2018
    • ready to start with next weekly
    • Expected availability by end of February
  • LDM-564 need to be updated
  • Gabriele Comoretto create issues documenting the actions to be performed to complete the release (release note, characterization report, etc)

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

DM-645 - Getting issue details... STATUS

DM-647 - Getting issue details... STATUS

DM-723 - Getting issue details... STATUS

DM-729 - Getting issue details... STATUS

DM-1495 - Getting issue details... STATUS

DM-996 - Getting issue details... STATUS

DM-1688 - Getting issue details... STATUS

DM-895 - Getting issue details... STATUS

DM-1470 - Getting issue details... STATUS

DM-1597 - Getting issue details... STATUS

  • A couple of issues have already been closed (DM-723, DM-729)
  • DM-996: reassigned to Gabriele Comoretto
  • Comment added on DM-1688, DM-895, DM-1495, DM-1470, and DM-1597
AOB




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#60 (2020 - 08 - 05)
Kian-Tat LimDMCCB#60 (2020 - 08 - 05)
  • 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)