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

Location

BrowserRoom SystemPhone Dial-in
https://bluejeans.com/761546516/
  1. Dial: 199.48.152.152 or bjn.vc
  2. Enter Meeting ID: 761546516 -or- use the pairing code

Dial-in numbers:

  • +1 408 740 7256
  • +1 888 240 2560 (US Toll-Free)
  • +1 408 317 9253 (Alternate Number)

Meeting ID: 761546516

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesday, April the 3rd.


Attendees

Regrets

DMCCB Meeting Goals

  • See DMCCB responsibilities listed in LDM-294 section 7.4

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-581 - Getting issue details... STATUS

  • No action to take by the DMCCB


Proposed RFCs

(to review, do not require DMCCB approval)

RFC-583 - Getting issue details... STATUS

RFC-585 - Getting issue details... STATUS

RFC-589 - Getting issue details... STATUS

  • RFC-583: wait until the end of the week
  • No comments from DMCCB on RFC-585 and RFC-589

Adopted RFCs without Triggering issues

(to create implementing DM issues)

None


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

None



RFCs adopted since last CCB

(to review, no action required)

None


RFCs implemented since last CCB

(to review, no action required)

RFC-587 - Getting issue details... STATUS

RFC-588 - Getting issue details... STATUS

RFC-578 - Getting issue details... STATUS

RFC-586 - Getting issue details... STATUS

RFC-584 - Getting issue details... STATUS

RFC-563 - Getting issue details... STATUS



Changes to the planned releases
  • 18.0 Release to be planned (no changes since last DMCCB)


Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity

  1. DM-2876 - Getting issue details... STATUS
  2. DM-2994 - Getting issue details... STATUS
  3. DM-3035 - Getting issue details... STATUS
  4. DM-3190 - Getting issue details... STATUS
  5. DM-708 - Getting issue details... STATUS
  6. DM-864 - Getting issue details... STATUS
  7. DM-1723 - Getting issue details... STATUS
  8. DM-2944 - Getting issue details... STATUS
  9. DM-889 - Getting issue details... STATUS
  10. DM-3201 - Getting issue details... STATUS

3927 unresolved issues (3827 on March. the 20th)


Pre-meeting homework:

  • DM-2876 is a reasonable, but very low priority, feature request.
  • DM-2994 is a low-impact (probable) bug in EUPS, with poor instructions to reproduce.
  • DM-3035, DM-864, DM-1723 are old DAX issues. I've asked Fritz Mueller to comment on whether they are still relevant.
  • DM-3190 is a docs ticket which we should act on.
  • Closed DM-708 as “Won't fix”.
  • DM-2944 just went into review (smile).
  • Marked DM-889 (an old epic full of complete stories) as “done”.
  • DM-3201 is a genuine issue, but has not been high enough priority to cause problems.
  • John Swinbank assess the issues that are still open, and a comment that the issues are still valid (DM-2876, DM-3190)
AOB




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)
22 Feb 2023Leanne GuyDMCCB#155 (2023 - 02 - 08)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
 Tim JennessDMCCB#51 (2020 - 05 - 27)