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.05 to 09.35 PT, Wednesday, December the 4th.
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: Oct/14/2019
-
RFC-645
-
Getting issue details...
STATUS
Planned end: Nov/13/2019
-
RFC-647
-
Getting issue details...
STATUS
Planned end: Dec/02/2019
| - RFC-620 no news
- RFC-645
- It should be an SST decision
- It is sometimes too precise in the check
- A different check that the numbers a reasonable right may be needed
- Summarizing: Everybody seems to agree in the approval if something new is needed in a replacement needs to be discussed in a different ticket
- If approved, needs to be mentioned in the 19.0.0 release note
- RFC-647
- DMCCB agrees to board recommend
- This should be included in the conda env after release 19 is done
|
| 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: Dec/15/2019
|
|
Adopted RFCs without Triggering issues (to create implementing DM issues) |
|
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | | - Waiting for BVan to get the conda externals working
- To mark as done
|
RFCs adopted since last CCB (to review, no action required) | -
RFC-646
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) | -
RFC-642
-
Getting issue details...
STATUS
-
RFC-585
-
Getting issue details...
STATUS
-
RFC-625
-
Getting issue details...
STATUS
-
RFC-646
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned major release 19.0.0
| - Waiting on RFC-645 conclusions, if something needs to be added to the release note
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity -
DM-5817
-
Getting issue details...
STATUS
-
DM-6268
-
Getting issue details...
STATUS
-
DM-5216
-
Getting issue details...
STATUS
-
DM-4861
-
Getting issue details...
STATUS
-
DM-6329
-
Getting issue details...
STATUS
-
DM-5717
-
Getting issue details...
STATUS
-
DM-6295
-
Getting issue details...
STATUS
-
DM-5974
-
Getting issue details...
STATUS
-
DM-5944
-
Getting issue details...
STATUS
-
DM-6393
-
Getting issue details...
STATUS
3906 unresolved issues (3915 on November the 20th) | - DM-5817 — Frossie Economou
- DM-6268, DM-5216 — Frossie Economou (tickets still looks valid, but very low priority)
- DM-4861 — John Swinbank closed as invalid (work has been done elsewhere)
- DM-6329 — Seems valid, pending the result of System Mgmt question. Tim Jenness has commented, so this is punted into the future.
- DM-5717 — resolved in 2016; not sure why it's listed here.
- DM-6295 — Closed as won't fix.
- DM-5974 — Poked by Tim Jenness.
- DM-5944 — Frossie Economou. Not sure if this is still relevant given new SQuaSH implementation.
- DM-6393 — Poked by Tim Jenness. Not sure this is something we're ever going to do as a single piece of work though — seems more like something folks will do ad-hoc as they run across issues as part of other tickets.
|
| Open Actions |
|
|
| AOB |
|
|
| Next DM-CCB |
| December the 11th. |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
Task report
Looking good, no incomplete tasks.