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, May the 1st.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
Discussion Items
| Item | Description | CCB Notes |
|---|
Flagged RFCs (To be approved by the DMCCB) |
RFC-581
-
Getting issue details...
STATUS
Planned end: 15/Mar/19 | |
| Board Recommended RFCs |
RFC-592
-
Getting issue details...
STATUS
Planned end: 18/Feb/19 | |
Proposed RFCs (to review, do not require DMCCB approval) |
RFC-595
-
Getting issue details...
STATUS
Planned end: 02/May/19
RFC-585
-
Getting issue details...
STATUS
Planned end: 22/Apr/19
RFC-593
-
Getting issue details...
STATUS
Planned end: 13/May/19
RFC-594
-
Getting issue details...
STATUS
Planned end: 02/May/19 | - RFC-595: rationalize data packages outside the obs package
- RFC-594: it is fine for the DMCCB
- RFC-593: There is some pushback
- RFC-585
- End date needs to be moved forward
|
Adopted RFCs without Triggering issues (to create implementing DM issues) | | |
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | | |
RFCs adopted since last CCB (to review, no action required) | |
|
RFCs implemented since last CCB (to review, no action required) | |
|
| Changes to the planned releases | - 18.0 Release to be planned (no changes since the last DMCCB)
| - 18.0: end of cycle release
- start working end of May with due date end of June
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity -
DM-2358
-
Getting issue details...
STATUS
-
DM-2579
-
Getting issue details...
STATUS
-
DM-3198
-
Getting issue details...
STATUS
-
DM-2219
-
Getting issue details...
STATUS
-
DM-3665
-
Getting issue details...
STATUS
-
DM-3664
-
Getting issue details...
STATUS
-
DM-3191
-
Getting issue details...
STATUS
-
DM-3589
-
Getting issue details...
STATUS
-
DM-3413
-
Getting issue details...
STATUS
-
DM-3854
-
Getting issue details...
STATUS
4053 unresolved issues (4190 on April the 24th)
| Pre-meeting John Swinbankcommentary: - DM-2358: Won't Fix.
- DM-2579: Seems like a legit bug which I may have just fixed; .
- DM-3198: Invalid (“no longer a useful statement”).
- DM-2219: Won't Fix.
- DM-3665: Maybe Won't Fix? .
- DM-3664: Low priority, but valid.
- Comment added to the issue
- DM-3191: Won't Fix.
- DM-3589: A bit vague, but probably valid. Asked our current ISR guru to take a look.
- DM-3413: Probably invalid. Asked Gregory and Frossie (reporter and assignee, respectively) to confirm.
- DM-3854: Invalid.
|
| AOB | - Shall we look at document RFCs after adoption to make sure they are finished?
| - Tim Jenness : shall we start listing the adopted but not implemented LDMs?
- an adopted LDM RFC is almost 99% done.
- no objections from the DMCCB.
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions