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 8th.
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: Jan/15/2020
-
RFC-674
-
Getting issue details...
STATUS
Planned end: Mar/17/2020
-
RFC-681
-
Getting issue details...
STATUS
Planned end: Apr/07/2020
| - RFC-620: no updates
- RFC-674: comments agreed, waiting for some external review before moving forward
- RFC-681:
- Leanne Guy reviewed it, is good to go
- There may be some need for adjust the title
|
| Board Recommended RFCs | -
RFC-671
-
Getting issue details...
STATUS
| |
| Adopted but not implemented LDM RFCs (only document RFCs) |
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-685
-
Getting issue details...
STATUS
Planned end: Apr/10/2020
-
RFC-684
-
Getting issue details...
STATUS
Planned end: Apr/08/2020
-
RFC-683
-
Getting issue details...
STATUS
Planned end: Apr/07/2020
-
RFC-682
-
Getting issue details...
STATUS
Planned end: Apr/03/2020
-
RFC-680
-
Getting issue details...
STATUS
Planned end: Apr/01/2020
-
RFC-675
-
Getting issue details...
STATUS
Planned end: Mar/06/2020
-
RFC-662
-
Getting issue details...
STATUS
Planned end: Mar/26/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: Mar/31/2020
| - RFC-685:
- RFC-684
- RFC-683
- John Swinbank Merlin should retire the RFC
- a better solution should be proposed
- RFC-682
- it should not be problematic
- RFC-680
- RFC-675
- should be withdrawn and the requested library added to nublado
|
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) |
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) |
|
|
Releases - Planned
- Changes to the release schedule
| | - DM-22578 Colin Slater is going to look this week
- we should not be updating the demo constantly
- The deprecation issues can be done at the last minute
- Early May remains the date to start the release
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity. -
DM-3165
-
Getting issue details...
STATUS
-
DM-2296
-
Getting issue details...
STATUS
-
DM-1758
-
Getting issue details...
STATUS
-
DM-1976
-
Getting issue details...
STATUS
-
DM-2311
-
Getting issue details...
STATUS
-
DM-2378
-
Getting issue details...
STATUS
-
DM-2860
-
Getting issue details...
STATUS
-
DM-5211
-
Getting issue details...
STATUS
-
DM-1985
-
Getting issue details...
STATUS
-
DM-3972
-
Getting issue details...
STATUS
3999 unresolved issues (3884 on March the 11th) | 2296: Still relevant; low priority 2311: Still relevant; low priority 2378: Awaiting comment by John Gates 2860: Still relevant; moved to S20 query coverage epic
|
| Open Actions |
|
|
| AOB |
| - new cfitsio requires an RFC
- John Swinbank the process should be agreed
- Kian-Tat Lim is not a change to the API, but how the API is used, no way to put deprecation
- Tim Jenness it is still a backward incompatibility, we should be able to notify this as a deprecation
- Kian-Tat Lim is worried about adding a cycle delay in this type of changes
- An RFC may collect feedbacks if we need to deprecate the change, or just
|
| Next DM-CCB | April the 15th |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions