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, July the 15th.
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-711
-
Getting issue details...
STATUS
Planned end Jul/31/2020
-
RFC-710
-
Getting issue details...
STATUS
Planned end Jul/28/2020
-
RFC-709
-
Getting issue details...
STATUS
Planned end Jul/24/2020
-
RFC-708
-
Getting issue details...
STATUS
Planned end Jul/24/2020
-
RFC-707
-
Getting issue details...
STATUS
Planned end: Jul/10/2020
-
RFC-699
-
Getting issue details...
STATUS
Planned end: Jun/03/2020
-
RFC-695
-
Getting issue details...
STATUS
Planned end: Jul/31/2020
| |
| Board Recommended RFCs |
|
|
| Adopted but not implemented LDM RFCs (only document RFCs) |
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-703
-
Getting issue details...
STATUS
Planned end: Jun/30/2020
-
RFC-697
-
Getting issue details...
STATUS
Planned end: June/12/2020
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Jun/7/2021
|
|
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) | -
RFC-706
-
Getting issue details...
STATUS
-
RFC-704
-
Getting issue details...
STATUS
-
RFC-705
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) | -
RFC-672
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned Release 21.0.0
- Tentative schedule: November 2020
|
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity. -
DM-6055
-
Getting issue details...
STATUS
-
DM-697
-
Getting issue details...
STATUS
-
DM-1995
-
Getting issue details...
STATUS
-
DM-9294
-
Getting issue details...
STATUS
-
DM-5752
-
Getting issue details...
STATUS
-
DM-7914
-
Getting issue details...
STATUS
-
DM-1780
-
Getting issue details...
STATUS
-
DM-9197
-
Getting issue details...
STATUS
-
DM-4126
-
Getting issue details...
STATUS
-
DM-9142
-
Getting issue details...
STATUS
3893 unresolved issues (3883 on July the 8th) | - DM-6055: Still seems relevant to my naive eye; no idea if it has been addressed internally.
- DM-1995: I think this is still true. It's a painful Jira Agile misfeature, but it seems unlikely that we will ever actually fix it. Suggest closing this as Won't Fix.
- DM-9294: Tim has commented (and perhaps we can just remove the code and close this issue).
- DM-7914: Added comment.
- DM-1780: Added comment.
- DM-4126: Nearly five years later, and this continues to be tiresome. Added comment.
|
| Open Actions |
|
|
| AOB |
|
|
| Next DM-CCB | July the 22nd |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions