Data Management
Space shortcuts
Page tree
Skip to end of metadata
Go to start of metadata

Location

Zoom link available on Slack channel.

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesday, September 1st, 2021.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescription

CCB Notes

Flagged RFCs

(To be approved by the DMCCB)

  • RFC-771 - Getting issue details... STATUS Planned end: Apr/21/2021

  • RFC-783 - Getting issue details... STATUS Planned end: July/31/2021

  • RFC-795 - Getting issue details... STATUS 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

Board Recommended RFCs
  • RFC-785 - Getting issue details... STATUS
  • RFC-800 - Getting issue details... STATUS
  • RFC-798 - Getting issue details... STATUS
  • RFC-799 - Getting issue details... STATUS




Adopted but not implemented LDM RFCs (only document RFCs)



Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-797 - Getting issue details... STATUS

small disscussion with Leanne on keeping this like running task in shell -  you can override the log setting the notebook (set to off) - so ok. CCB do not need to approve this

 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)

  • RFC-796 - Getting issue details... STATUS


RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)

  • RFC-638 - Getting issue details... STATUS
  • RFC-793 - Getting issue details... STATUS





Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 23.0.0:
    • DM-29437 - Getting issue details... STATUS  
    • 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)
  1. DM-12932 - Getting issue details... STATUS
  2. DM-13034 - Getting issue details... STATUS
  3. DM-12671 - Getting issue details... STATUS
  4. DM-9575 - Getting issue details... STATUS
  5. DM-10232 - Getting issue details... STATUS
  6. DM-13044 - Getting issue details... STATUS
  7. DM-13071 - Getting issue details... STATUS
  8. DM-13089 - Getting issue details... STATUS
  9. DM-13092 - Getting issue details... STATUS
  10. DM-13097 - Getting issue details... STATUS

Unresolved issues: 4126


Open Actions

AOB



Next DM-CCB September 15th


Pending Flagged RFCs

Key Summary
Refresh

Pending Proposed RFCs

Key Summary
Refresh

Oldest issues

Key Summary
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
  • Tim Jenness investigate astropy warnings filter for tests.
05 Oct 2022Tim JennessDMCCB#142 (2022 - 09 - 28)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
 Tim JennessDMCCB#51 (2020 - 05 - 27)