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, Wednesdays.


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-842 - Getting issue details... STATUS
  • RFC-859 - Getting issue details... STATUS
  • RFC-861 - Getting issue details... STATUS
  • RFC-865 - Getting issue details... STATUS
  • 771 - Awaiting Gregory Dubois-Felsmann
  • Agreed that getCalspec can be added to rubin-env.
  • Jim Bosch will take a look at RFC-861.
  • Decided that we should not switch to mkl until we need to.
Board Recommended RFCs
  • RFC-850 - Getting issue details... STATUS
  • RFC-858 - Getting issue details... STATUS
  • RFC-855 - Getting issue details... STATUS
  • RFC-856 - Getting issue details... STATUS
  • RFC-828 - Getting issue details... STATUS


Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-823 - Getting issue details... STATUS
  • RFC-863 - Getting issue details... STATUS
  • RFC-860 - Getting issue details... STATUS
  • RFC-862 - Getting issue details... STATUS


  • Agreed to flag RFC-863.
  • Jim Bosch requested we flag and then board recommend RFC-860 and the board agreed.

 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-853 - Getting issue details... STATUS
  • RFC-857 - Getting issue details... STATUS
  • RFC-840 - Getting issue details... STATUS
  • RFC-854 - Getting issue details... STATUS
  • RFC-864 - Getting issue details... STATUS

The board agreed that RFC-864 was implicitly approved as part of RFC-853.

RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)

  • RFC-825 - Getting issue details... STATUS
  • RFC-809 - Getting issue details... STATUS
  • RFC-836 - Getting issue details... STATUS





Releases

  • Planned
  • Changes to the release schedule
  • Next planned Releases 23.0.3? and 24.0.0
    • paperwork ticket:   DM-34982 - Getting issue details... STATUS


23.0.2 release is the dp0.2 processing release. There will be a 23.0.3.

24.0 will likely be based off w.2022.24 with backports known to be needed.

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-16378 - Getting issue details... STATUS
  2. DM-5440 - Getting issue details... STATUS
  3. DM-16466 - Getting issue details... STATUS
  4. DM-16520 - Getting issue details... STATUS
  5. DM-16511 - Getting issue details... STATUS
  6. DM-16512 - Getting issue details... STATUS
  7. DM-16523 - Getting issue details... STATUS
  8. DM-16590 - Getting issue details... STATUS
  9. DM-16571 - Getting issue details... STATUS
  10. DM-16591 - Getting issue details... STATUS

Unresolved issues: 4235



Open Actions



AOB



Next DM-CCB June 29, 2022


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  to write a policy on how external code written by DM shall be handled.
 Tim JennessDMCCB#51 (2020 - 05 - 27)