Versions Compared

Old Version 14

changes.mady.by.user Kian-Tat Lim

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (mbutler)

Saved on

Key

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

Location:  No face to face meeting today.  

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

...

ItemDescriptionCCB Notes
New Baselined Items
  • LDM documents
  • Products in the product tree
  • 3 LDMs to put in docushare:
    RFC-495 (
      • LDM-639
    )
      • :
      •  Leanne Guy Leanne to check RFC-516 (
        Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-495
      • LDM-542
    )
      • :
      •  Tim Jenness to fix
        Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-
    530 (
      • 516
      • LDM-148
    ): KT to check
      • :
      •  Kian-Tat Lim to check
        Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-530
        (done)


    Changes to Baselined Items
    • LDM-533 (RFC-568)
    • LDM-294 (RFC-561)
    • Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyRFC-561
      (LDM-294): DMCCB changes are OK, Product Tree stuff need more work
      • Product Tree will be a continuous improvement process
    • Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyRFC-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
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyRFC-538
      (LDM-151): KT to finish it today


    Changes to the planned releases
    • 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
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-569
        to be accepted first.


    Review / approve RFCs

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

    • Proposed / Flagged RFCs

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


    •  Kian-Tat Lim to close
      Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyRFC-567
    : KT to close it
    • (done)
    • Jira
      serverJIRA
      serverId
    RFC-566: OK
    • 9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyRFC-566
      no action from the CCB
    •  John Swinbank to adopt
      Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyRFC-565
    : John to adopt it
    • as is
      RFC-563: GCM
      it
    • RFC-557: KT to adopt it (done)
    • RFC-552: json to be added
    • RFC-541: JBosh
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-563
      •  Kian-Tat Lim to adopt
        Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-557
        (done)
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-552
        to be discussed offline
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-541
        no action from the CCB
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-538
        no action from the CCB
      RFC-538:

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

      To ensure that all adopted RFC have a triggered issue.

      Adopted RFC that requires triggered issues:

      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyRFC-134
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        key
      RFC-134
      • RFC-150
      Monitor Jira issues status

      Support to J. Swinbank monitoring activity

      • 3526 Unresolved DM issues
      • the 10 oldest (last Updated in 2016 and 2017) per priority:
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-10001
          Blocker, last updated 2017/04/25
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-9085
          Blocker, last updated 2017/10/02
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-10209
          Blocker, last updated 2017/10/02
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-303
          Critical, last updates 2016/03/03
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-965
          Critical, last updated 2016/03/08
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-5739
          Critical, last updated 2016/04/08
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-4531
          Critical, last updated 2016/10/12
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-9742
          Critical, last updated 2017/03/08
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-9980
          Critical, last updated 2017/04/10
        • Jira
          serverJIRA
          serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
          keyDM-11879
          Critical, last updated 2017/09/11
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-10001
        :
        comment added
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-9085
        :
        comment added
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-10209
        :
        issue closed as "Won't Fix"
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-303
        :
        issue closed as "Won't Fix"
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-965
        :
        issue closed as "Won't Fix"
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-5739
        :
      • DM-4531: comment added
      • DM-9742:
      • DM-9980:
      • changed to minor improvement; original bug was found to be invalid
      • Jira
        serverJIRA
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-4531
        comment added        DM-11879:


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


      DM Risks

      DMCCB should monitor risks related on DMCCBto DM.

      Risks managed in Jira RM project.


      Meeting outcome
      •  Unknown User (gcomoretto) Tim Jennessto integrate in the preparation of the DMCCB agenda, the existing reports on RFCs requiring triggering issues and to be marked as implemented.

      ...