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, April the 29th.
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-674
-
Getting issue details...
STATUS
Planned end: Mar/17/2020
| - RFC-674: GCM working on it
|
| Board Recommended RFCs | -
RFC-689
-
Getting issue details...
STATUS
-
RFC-620
-
Getting issue details...
STATUS
| - RFC-689
- some problems have been resolved
- some problems still there: use repos.yaml in tagging
- we are stopped on step 2 of 15
- this patch release is discovering problems that we would have in 20.0.0 in any case, so it is worth doing it.
- If 19.0.1 can't be done this week, we stop and move forward to 20.0.0
- RFC-620: it is up to Mario to adopt it
|
| Adopted but not implemented LDM RFCs (only document RFCs) |
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-690
-
Getting issue details...
STATUS
Planned end: Apr/28/2020
-
RFC-688
-
Getting issue details...
STATUS
Planned end: Apr/23/2020
-
RFC-686
-
Getting issue details...
STATUS
Planned end: Apr/15/2020
-
RFC-685
-
Getting issue details...
STATUS
Planned end: Apr/10/2020
-
RFC-680
-
Getting issue details...
STATUS
Planned end: Apr/01/2020
-
RFC-675
-
Getting issue details...
STATUS
Planned end: Mar/06/2020
-
RFC-652
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-651
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Apr/30/2020
| - RFC-686 should be adopted
- Lots if the proposed RFCs are just waiting for the new conda-forge based environment
- it seems that Brian already included
|
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-662
-
Getting issue details...
STATUS
-
RFC-687
-
Getting issue details...
STATUS
-
RFC-691
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) |
|
|
Releases - Planned
- Changes to the release schedule
| | - Colin Slater working on the stack demo replacement
- suggest to add the new stack demo after the release
- timing
- if we start Monday, we shall close all blocker by Thursday or postpone them to 21.0
- John Swinbank setup a pipeline task force to try to fix:
- DM-20573
- DM-21711
- DM-22192
- DM-23343
- DM-24565
- DM-22233 WOM will try to fix it
- DM-23374 postponed to 21.0
- DM-22578 postponed to 21.0
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity. -
DM-8236
-
Getting issue details...
STATUS
-
DM-8301
-
Getting issue details...
STATUS
-
DM-8285
-
Getting issue details...
STATUS
-
DM-8416
-
Getting issue details...
STATUS
-
DM-7625
-
Getting issue details...
STATUS
-
DM-7721
-
Getting issue details...
STATUS
-
DM-8442
-
Getting issue details...
STATUS
-
DM-7375
-
Getting issue details...
STATUS
-
DM-4624
-
Getting issue details...
STATUS
-
DM-8410
-
Getting issue details...
STATUS
3963 unresolved issues (3967 on April the 22nd) | DM-8236: pending info from Nate Pease DM-7625: still relevant |
| Open Actions |
|
|
| AOB |
|
|
| Next DM-CCB | May the 6th |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions