Flagged RFCs
(To be approved by the DMCCB)
Planned end: Jan/15/2020
Proposed RFCs
(to review, do not require DMCCB approval)
Planned end: Jan/31/2020
Planned end: Dec/13/2019
Planned end: Dec/13/2019
Planned end: Jan/22/2020
Planned end: Jan/22/2020
Planned end: Jan/08/2020
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
- Next planned major release 20.0.0
Planned for Spring 2020
- Blocking issues open:
- Do we need a 20.0.1 patch?
- so far no RFC open
- see
and related discussion
- see
- so far no RFC open
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Support to J. Swinbank monitoring activity
3771 unresolved issues (3858 on December the 18th)
- DM-6025: Has been done, closed as duplicate.
- DM-5951: Has been done, closed as duplicate.
- DM-6152: Done.
- DM-6594: Has been done, closed as duplicate.
- DM-6571: A long-standing (since 2014) deprecation. I (John Swinbank) propose that we make this ticket block the next release. Does the DM-CCB concur? Note that it will cause a publicly-visible API change, but one that has been in the offing for six years.
- I propose to close DM-6602 as “won't fix”, on the basis that LDM-472 is obsolete. We should also officially mark LDM-472 as obsolete. But we should discuss all this with Wil O'Mullane before doing so.
- DM-5721: Won't fix.
- DM-5857: Still valid; added comment.
- DM-5862: As DM-5857.
- DM-5724: Has been marked as “won't fix” since December 2019; not sure why it appears on this list.
