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:
- Leanne Guy Leanne to check
Jira |
---|
server | JIRA |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-495 |
---|
|
- Tim Jenness to fix
Jira |
---|
server | JIRA |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-516 |
---|
|
- Kian-Tat Lim to check
Jira |
---|
server | JIRA |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-530 |
---|
| (done)
|
Changes to Baselined Items | - LDM-533 (RFC-568)
- LDM-294 (RFC-561)
| 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
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
|
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 |
---|
server | JIRA |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-569 |
---|
| to be accepted first.
|
Review / approve RFCs | Should we add a new status: "Ready for CCB" Jira |
---|
server | JIRA |
---|
columns | key,summary |
---|
maximumIssues | 20 |
---|
jqlQuery | project = rfc and status in( proposed, flagged) |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
|
|
- 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
- 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 |
---|
|
|
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 |
---|
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).
|
DM Risks |
| DMCCB should monitor risks related to DM. Risks managed in Jira RM project. |
Meeting outcome