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, September the 16th.
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-709
-
Getting issue details...
STATUS
Planned end Jul/24/2020
-
RFC-699
-
Getting issue details...
STATUS
Planned end: Sep/04/2020
-
RFC-695
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
| - RFC-709
- Still pending Leanne to review the proposed text.
- RFC-699
- RFC-695
- No action required for the moment, due date end of the month
|
Board Recommended RFCs |
|
|
Adopted but not implemented LDM RFCs (only document RFCs) | -
RFC-710
-
Getting issue details...
STATUS
- waiting for LCR-2643 to finish
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-727
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
-
RFC-726
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
-
RFC-723
-
Getting issue details...
STATUS
Planned end: Aug/31/2020
-
RFC-703
-
Getting issue details...
STATUS
Planned end: Aug/31/2020
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Jun/7/2021
| - RFC-727, there should not be any problem
- RFC-703
- We should just adopt it, but it is not going to affect any LDM document
- Developer guidelines should be updated to point to this procedure
- It does not require CCB approval
|
Adopted RFCs without Triggering issues (to create implementing DM issues) | -
RFC-710
-
Getting issue details...
STATUS
(waiting for LCR-2643)
-
RFC-697
-
Getting issue details...
STATUS
|
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | -
RFC-484
-
Getting issue details...
STATUS
|
|
RFCs adopted since the last DMCCB (to review, no action required) | -
RFC-722
-
Getting issue details...
STATUS
-
RFC-725
-
Getting issue details...
STATUS
-
RFC-697
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since the last DMCCB (to review, no action required) | -
RFC-698
-
Getting issue details...
STATUS
-
RFC-484
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned Release 21.0.0
- Tentative schedule: November 2020
| - Yusra should take responsibility to have the list of issues for the release, deprecation, etc.
- Invite Yusra to the CCB will be beneficial for the process.
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity. -
DM-9858
-
Getting issue details...
STATUS
-
DM-9708
-
Getting issue details...
STATUS
-
DM-9563
-
Getting issue details...
STATUS
-
DM-9804
-
Getting issue details...
STATUS
-
DM-9709
-
Getting issue details...
STATUS
-
DM-9611
-
Getting issue details...
STATUS
-
DM-9397
-
Getting issue details...
STATUS
-
DM-9369
-
Getting issue details...
STATUS
-
DM-9357
-
Getting issue details...
STATUS
-
DM-9273
-
Getting issue details...
STATUS
3935 unresolved issues (3942 on September the 9th) | - DM-9858 — being worked on by the Architecture team.
- DM-9708 — still a valid issue; low priority; added comment.
- DM-9563 — suspect this is no longer relevant; added comment.
- DM-9709 — still seems valid; low priority; added comment.
- DM-9273 — still seems valid; low priority; added comment.
|
Open Actions |
| |
AOB | | - John should transfer his open tickets before he lives
|
Next DM-CCB | September 23rd. |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
Task report
Looking good, no incomplete tasks.