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 9th.
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-722
-
Getting issue details...
STATUS
Planned end Aug/27/2020
-
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-722
- KT and Tim agrees that may be good to have an EUPS package
- Wil has some concerns in having an additional fork
- Tim commented that who is working on it is paid by the project, therefore should not be a project
- KT to comment on it
- CCB agreed to board recommend it
- RFC-709
- RFC-699 Still waiting for some work done. Architecture could take it over, but it probably can wait.
- Tim: it requires some test infrastructure
- It requires also a change in the dev guide as per John's comment
- RFC-695: due end of September
|
| Board Recommended RFCs |
|
|
| Adopted but not implemented LDM RFCs (only document RFCs) | -
RFC-710
-
Getting issue details...
STATUS
| - RFC-710: waiting for LCR to finish
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-726
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
-
RFC-725
-
Getting issue details...
STATUS
Planned end: Sep/2/2020
-
RFC-724
-
Getting issue details...
STATUS
Planned end: Sep/17/2020
-
RFC-723
-
Getting issue details...
STATUS
Planned end: Aug/31/2020
-
RFC-703
-
Getting issue details...
STATUS
Planned end: Aug/31/2020
-
RFC-697
-
Getting issue details...
STATUS
Planned end: June/11/2020
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Jun/7/2021
| - RFC-725: python 3.8
- flagged
- nobody object
- requires a new environment
- CCB agreed that it can be board recommended
- RFC-724 should not be here, T&S
- RFC-723 requires some more details
|
Adopted RFCs without Triggering issues (to create implementing DM issues) | -
RFC-719
-
Getting issue details...
STATUS
-
RFC-710
-
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-708
-
Getting issue details...
STATUS
-
RFC-710
-
Getting issue details...
STATUS
-
RFC-711
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since the last DMCCB (to review, no action required) | -
RFC-708
-
Getting issue details...
STATUS
-
RFC-711
-
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-7883
-
Getting issue details...
STATUS
-
DM-3550
-
Getting issue details...
STATUS
-
DM-9037
-
Getting issue details...
STATUS
-
DM-9324
-
Getting issue details...
STATUS
-
DM-9065
-
Getting issue details...
STATUS
-
DM-9289
-
Getting issue details...
STATUS
-
DM-8710
-
Getting issue details...
STATUS
-
DM-5195
-
Getting issue details...
STATUS
-
DM-6619
-
Getting issue details...
STATUS
-
DM-7885
-
Getting issue details...
STATUS
3942 unresolved issues (3925 on August the 26th) | - DM-6619 obsolete
- DM-7883 won't fix
|
| Open Actions |
| |
| AOB | | |
| Next DM-CCB | September 16th. |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions