DMCCB#2 (2019-01-23)

• 3 LDMs to put in docushare:
  • LDM-639 :
  • Leanne Guy Leanne to check RFC-495 - Getting issue details... STATUS
  • LDM-542:
  • Tim Jenness to fix RFC-516 - Getting issue details... STATUS
  • LDM-148:
  • Kian-Tat Lim to check RFC-530 - Getting issue details... STATUS (done)

• RFC-561 - Getting issue details... STATUS (LDM-294): DMCCB changes are OK, Product Tree stuff need more work
  • Product Tree will be a continuous improvement process
  • Unknown User (gcomoretto) To open a ticket on the remaining comments in the product tree
• RFC-568 - Getting issue details... STATUS (LDM-533):
  • Still level 1? Issue the document. In the long term the documents need to be reworked following the product tree.
  • The document to be approve as is.
• RFC-538 - Getting issue details... STATUS (LDM-151): KT to finish it today

• 17.0 planned for end of 2018, shifted at the beginning of 2019
• LDM-564 need to be updated

• work ongoing on the 17.0 blocking issues
  • RFC-569 - Getting issue details... STATUS to be accepted first.

Should we add a new status: "Ready for CCB"

• Proposed / Flagged RFCs

• 66 RFCs in status Adopted

• Kian-Tat Lim to close RFC-567 - Getting issue details... STATUS (done)

• RFC-566 - Getting issue details... STATUS no action from the CCB

• John Swinbank to adopt RFC-565 - Getting issue details... STATUS as is

• Unknown User (gcomoretto) to take care of RFC-563 - Getting issue details... STATUS

• Kian-Tat Lim to adopt RFC-557 - Getting issue details... STATUS (done)

• RFC-552 - Getting issue details... STATUS to be discussed offline
• RFC-541 - Getting issue details... STATUS no action from the CCB
• RFC-538 - Getting issue details... STATUS no action from the CCB

Once RFC are adopted, TCAM/s need to ensure that they are implemented. To bring up at DMLT.

Adopted RFC that requires triggered issues:

• RFC-134 - Getting issue details... STATUS
• RFC-150 - Getting issue details... STATUS

Support to J. Swinbank monitoring activity

• 3526 Unresolved DM issues
• the 10 oldest (last Updated in 2016 and 2017) per priority:
  • DM-10001 - Getting issue details... STATUS Blocker, last updated 2017/04/25
  • DM-9085 - Getting issue details... STATUS Blocker, last updated 2017/10/02
  • DM-10209 - Getting issue details... STATUS Blocker, last updated 2017/10/02
  • DM-303 - Getting issue details... STATUS Critical, last updates 2016/03/03
  • DM-965 - Getting issue details... STATUS Critical, last updated 2016/03/08
  • DM-5739 - Getting issue details... STATUS Critical, last updated 2016/04/08
  • DM-4531 - Getting issue details... STATUS Critical, last updated 2016/10/12
  • DM-9742 - Getting issue details... STATUS Critical, last updated 2017/03/08
  • DM-9980 - Getting issue details... STATUS Critical, last updated 2017/04/10
  • DM-11879 - Getting issue details... STATUS Critical, last updated 2017/09/11

• DM-10001 - Getting issue details... STATUS comment added
• DM-9085 - Getting issue details... STATUS comment added
• DM-10209 - Getting issue details... STATUS issue closed as "Won't Fix"
• DM-303 - Getting issue details... STATUS issue closed as "Won't Fix"
• DM-965 - Getting issue details... STATUS issue closed as "Won't Fix"
• DM-5739 - Getting issue details... STATUS changed to minor improvement; original bug was found to be invalid
• DM-4531 - Getting issue details... STATUS comment added

Discussion on the reason to bring old issues at the attention of the DMCCB:

• • John Swinbank : DM is missing a definition of priorities
  • Wil O'Mullane : how are we dealing with real critical tickets from the mountain?
  • to be discussed at DMLT
  • to see SE approach about priority

For next DMCCB, to consider just the 10 oldest (the priority is not relevant).