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)
CANCELLED
Time
From 9.05 to 09.35 PT, Wednesday, January the 8th.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
DMCCB Additional Resources
Discussion Items
| Item | Description | CCB Notes |
|---|
Flagged RFCs (To be approved by the DMCCB) | -
RFC-620
-
Getting issue details...
STATUS
Planned end: Jan/15/2020
|
|
| Board Recommended RFCs |
|
|
| Adopted but not implemented LDM RFCs (only document RFCs) |
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-638
-
Getting issue details...
STATUS
Planned end: Jan/31/2020
-
RFC-648
-
Getting issue details...
STATUS
Planned end: Dec/13/2019
-
RFC-650
-
Getting issue details...
STATUS
Planned end: Dec/13/2019
-
RFC-651
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-652
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-653
-
Getting issue details...
STATUS
Planned end: Jan/08/2020
|
|
Adopted RFCs without Triggering issues (to create implementing DM issues) |
|
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | -
RFC-243
-
Getting issue details...
STATUS
|
|
RFCs adopted since last CCB (to review, no action required) | -
RFC-654
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) | -
RFC-654
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned major release 20.0.0
- Do we need a 20.0.1 patch?
- so far no RFC open
- see
DM-22703
-
Getting issue details...
STATUS
and related discussion
|
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity -
DM-6025
-
Getting issue details...
STATUS
-
DM-5951
-
Getting issue details...
STATUS
-
DM-6152
-
Getting issue details...
STATUS
-
DM-6594
-
Getting issue details...
STATUS
-
DM-6571
-
Getting issue details...
STATUS
-
DM-6602
-
Getting issue details...
STATUS
-
DM-5721
-
Getting issue details...
STATUS
-
DM-5857
-
Getting issue details...
STATUS
-
DM-5862
-
Getting issue details...
STATUS
-
DM-5724
-
Getting issue details...
STATUS
3771 unresolved issues (3858 on December the 18th) | - DM-6025: Has been done, closed as duplicate.
- DM-5951: Has been done, closed as duplicate.
- DM-6152: Done.
- DM-6594: Has been done, closed as duplicate.
- DM-6571: A long-standing (since 2014) deprecation. I (John Swinbank) propose that we make this ticket block the next release. Does the DM-CCB concur? Note that it will cause a publicly-visible API change, but one that has been in the offing for six years.
- I propose to close DM-6602 as “won't fix”, on the basis that LDM-472 is obsolete. We should also officially mark LDM-472 as obsolete. But we should discuss all this with Wil O'Mullane before doing so.
- DM-5721: Won't fix.
- DM-5857: Still valid; added comment.
- DM-5862: As DM-5857.
- DM-5724: Has been marked as “won't fix” since December 2019; not sure why it appears on this list.
|
| Open Actions |
|
|
| AOB |
|
|
| Next DM-CCB |
|
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions