Flagged RFCs
(To be approved by the DMCCB)
Planned end: Jul/31/2019
Planned end: Jun/26/2019
Planned end: Jul/15/2019
Planned end: Jul/15/2019
Planned end: Jul/18/2019
Planned end: Aug/02/2019
Planned end: Jul/19/2019
Planned end: Jul/24/2019
- RFC-593: waiting for KT
- due date has been moved to July 31
- RFC-605: from the comments, it seems that Jim and Robert have converged. The proposal is not to block the RFC on a technote, but consider the technote as an implementation detail.
- Tim Jenness is the DMCCB requested to board recommend this RFC?
- Tim Jennessto comment RFC-605 and reset it to Proposed
- Tim Jenness is the DMCCB requested to board recommend this RFC?
- RFC-611: board recommended
- RFC-612: board recommended
- RFC-615: still no time to reviewing the costs... so better to withdraw the RFC
- new cost model should be traced on a Jira issue. John Swinbankcommented that there should be 2 Jira issues, one for the short term changes and one for the long term changes
- Kian-Tat Lim to open an issue to review the cost model in the short term
- Unknown User (mbutler) to find which issue is tracing the long term cost model activity
- new cost model should be traced on a Jira issue. John Swinbankcommented that there should be 2 Jira issues, one for the short term changes and one for the long term changes
- RFC-617: nothing to do
- RFC-619: board recommended
- RFC-620: it seems that this RFC will require much more time in order to be resolved, probably until the PCW, however, we need something for the review
- John Swinbank says the proposed draft documents should be good for the review
- Kian-Tat Lim had a look at them and it seems that what proposed is OK
- Leanne Guy and SST to check the DPDD changes proposed in RFC-620
- Tim Jenness to look at LSE-61 requirements changes by RFC-620
- John Swinbank to look at the proposed LDM-151 changes in RFC-620
None
None
Proposed RFCs
(to review, do not require DMCCB approval)
Planned end: Jul/19/2019
Planned end: Jun/14/2019
Adopted RFCs without Triggering issues
(to create implementing DM issues)
None
Adopted RFCs with all triggered work COMPLETED
(to set status as 'IMPLEMENTED')
- Tim Jenness will talk to Nate afeter the meeting
RFCs adopted since last CCB
(to review, no action required)
RFCs implemented since last CCB
(to review, no action required)
- Next Releases:
- Accepted 18.1.0 as per
- Jira issue
- Next Major release 19.0.0
- Autumn 2019
- 18.1.0
- backport done
- first release candidate ready to go
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Support to J. Swinbank monitoring activity
4019 unresolved issues (3957 on July the 17th)
From Fritz:
- DM-2722, DM-616: May still be relevant (but may not because of config in Kubernetes world). Fabrice needs to comment on these when he returns from holiday.
- DM-2313: Still relevant, but a low priority optimization and hard to predict actual gain.
- DM-3781 is still valid, low priority.
