Page History

• 3 LDMs to put in docushare:
  • LDM-639 :
  •  Leanne Guy Leanne to check

    Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-495

  • LDM-542:
  •  Tim Jenness to fix

    Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-516

  • LDM-148:
  •  Kian-Tat Lim to check

    Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-530

    (done)

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-561

  (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

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-568

  (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.

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-538

  (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

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-569

    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

  Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-567

  (done)

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-566

  no action from the CCB

•  John Swinbank to adopt

  Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-565

  as is

• Unknown User (gcomoretto) to take care of

  Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-563

•  Kian-Tat Lim to adopt

  Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-557

  (done)

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-552

  to be discussed offline

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-541

  no action from the CCB

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-538

  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:

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-134

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key RFC-150

Support to J. Swinbank monitoring activity

• 3526 Unresolved DM issues
• the 10 oldest (last Updated in 2016 and 2017) per priority:

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-10001

    Blocker, last updated 2017/04/25

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-9085

    Blocker, last updated 2017/10/02

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-10209

    Blocker, last updated 2017/10/02

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-303

    Critical, last updates 2016/03/03

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-965

    Critical, last updated 2016/03/08

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-5739

    Critical, last updated 2016/04/08

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-4531

    Critical, last updated 2016/10/12

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-9742

    Critical, last updated 2017/03/08

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-9980

    Critical, last updated 2017/04/10

  • Jira
    server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-11879

    Critical, last updated 2017/09/11

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-10001

  comment added

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-9085

  comment added

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-10209

  issue closed as "Won't Fix"

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-303

  issue closed as "Won't Fix"

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-965

  issue closed as "Won't Fix"

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-5739

  changed to minor improvement; original bug was found to be invalid

• Jira
  server JIRA serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-4531

  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).