You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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 January the 23rd.

Attendees

Regrets

DMCCB Meeting Goals

Discussion Items

ItemDescriptionCCB Notes
New Baselined Items
  • LDM documents
  • Products in the product tree
  • 3 LDMs to put in docushare:
    • RFC-495 (LDM-639): Leanne to check
    • RFC-516 (LDM-542): Tim to fix
    • RFC-530 (LDM-148): KT to check


Changes to Baselined Items
  • LDM-533 (RFC-568)
  • LDM-294 (RFC-561)
  • RFC-561 (LDM-294): DMCCB changes are OK, Product Tree stuff need more work
    • Product Tree will be a continuous improvement process
    • To open a ticket on the remaining comments in the product tree
  • 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.
  • RFC-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
    • RFC-569 to be accepted.
Review / approve RFCs

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

  • Proposed / Flagged RFCs

Key Summary
Refresh

  • RFC-567: KT to close it
  • RFC-566: OK
  • RFC-565: John to adopt it as is
  • RFC-563: GCM to take care of it
  • RFC-557: KT to adopt it
  • RFC-552: json to be added
  • RFC-541: JBosh
  • 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.

  • 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:
    • 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: comment added
  • DM-9085: comment added
  • DM-10209: issue closed as "Won't Fix"
  • DM-303:
  • DM-965: issue closed as "Won't Fix"
  • DM-5739:
  • DM-4531: comment added
  • DM-9742:
  • DM-9980:
  • 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.


DM Risks

DMCCB should monitor risks related on DMCCB.

Risks managed in Jira RM project.


Meeting outcome


Task report

Looking good, no incomplete tasks.


  • No labels