CCB Notes
Flagged RFCs
(To be approved by the DMCCB)
Planned end: Apr/21/2021
Planned end: July/31/2021
Planned end: Aug/24/2021
Gregory
783 - needs migration script or plan for compatability. Generic formatter since its just a propertyset. Would be easy if it was a special metadata class which is the end result. Migration script was resisted. Old code will not be able to read the new metadata since the class will not exist in the old code. Jim prefers a migration script . KT wants to wait and see about collection based dataset... Colin thinks new name may be good. Can release code for first class metadata class - before migration script (8 weeks say) ..would also require the formatter. Per collection data types - schema change requires RFC - Jim thinks its non unique but not per dataset..
795 - board recommends
Proposed RFCs
(to review, do not require DMCCB approval)
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 the last DMCCB
(to review, no action required)
RFCs implemented (or withdrawn) since the last DMCCB
(to review, no action required)
Releases
- Planned
- Changes to the release schedule
- Next planned Release 23.0.0:
- Will be linked to version that we are confident will be used for the final DP0.2 run.
- Patch releases
- None
Monitor Jira issues status:
- the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
Unresolved issues: 4126
