Location
Browser | Room System | Phone Dial-in |
---|
https://bluejeans.com/761546516/ | - Dial: 199.48.152.152 or bjn.vc
- 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
Item | Description | CCB Notes |
---|
New Baselined Items | - LDM documents
- Products in the product tree
| - 3 LDMs to put in docushare:
|
Changes to Baselined Items | - LDM-533 (RFC-568)
- LDM-294 (RFC-561)
| -
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
-
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
|
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
-
Getting issue details...
STATUS
to be accepted first.
|
Review / approve RFCs | Should we add a new status: "Ready for CCB"
|
-
RFC-566
-
Getting issue details...
STATUS
no action from the CCB
-
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
|
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
-
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).
|
DM Risks |
| DMCCB should monitor risks related to DM. Risks managed in Jira RM project. |
Meeting outcome