Versions Compared

Old Version 20

changes.mady.by.user Leanne Guy

Saved on

compared with

New Version 21

changes.mady.by.user Leanne Guy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

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)

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-573

  • Requires experts for discussion, Jim Bosch or Robert Lupton
  • Note that Jim & Robert have now okayed the approach being taken on the RFC — I suggest that's probably all the input we need from them.

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-575

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-574


  • RFC-573
    • input provided by Jim and Robert in the RFC, they are fine with the proposal
    • RFC set to "Board Recommend"
  • RFC-575
    • John flagged this RFC in order to bring this attention to Leanne
    • All external stakeholders using weekly, need to be addressed to which weekly to use.
  • RFC-574
    • RFC adopted since it is a document

Proposed RFCs

(to review, do not require DMCCB approval)

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-576

  • RFC-576
    • Tim Jenness commented that the first part of the RFC is agreed, but the second part need some developments
    • John Swinbank LSE-400 still need to be released in docushare,

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)

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-571

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-562

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-549



RFCs implemented since last CCB

(to review, no action required)

None


Changes to the planned releases
  • 17.0 planned for the end of 2018
    • Jira
      serverJIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyDM-17880

      • Jira
        serverJIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-17881
    • Expected availability by end of February
  • LDM-564 need to be updated


  • Unknown User (gcomoretto) explained the status of the release:
    • at the moment there is an issue on codekit connecting to GitHub API
  • John Swinbank asked for the status of thew release procedure
    • DMTN-106 drafted

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-945
  2. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-615
  3. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-591
  4. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-327
  5. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2196
  6. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2251
  7. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2252
  8. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2204
  9. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2260
  10. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-485

3674 unresolved issues (3671 on Feb. the 13th)


  • DM-945 : no activities since 2014, comment added
  • DM-615: reassigned
  • DM-591:
  • DM-327:
  • The other issues have been closed before the DMCCB telecon starts
  • DM-2276 updated by Leanne Guy during the DMCCB
AOB


  • Currently when the CCB marks a flagged RFC as "board recommended" it is required that the next step be "manager approves". Since the manager is on the CCB this step is superfluous and the CCB would like the workflow modified such that "Adopt RFC" is the next step after "board recommended" . This allows the proposer to adopt the RFC themselves and add the "is triggering" Jira tickets.
    •  Unknown User (gcomoretto) to update the dev guide with the RFC workflow update: Originator adopt a "Board Recommend" RFC after opening the triggering issue(s)
  • Colin Slater End dates of RFCs are not taken in account.
    • DMCCB can board recommend even if others are not OK.. or due date is not met still
    • only proposed RFC with problems or due date in the past need to be discussed by the DMCCB
  • Next week, on February the 27th, there is no DMCCB, since everybody will be in the DMLT Face 2 Face


Pending Flagged RFCs

Jira
serverJIRA
columnskey,summary
maximumIssues20
jqlQueryproject = rfc and status = flagged
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Pending Proposed RFCs
Jira
serverJIRA
columnskey,summary
maximumIssues20
jqlQueryproject = rfc and status = proposed
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
Oldest issues

Jira
serverJIRA
columnskey,summary
maximumIssues20
jqlQueryproject = dm and resolution = Unresolved order by updated asc
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Meeting outcome


Pending DMCCB Actions

Task report
spacesDM
labelsdmccb