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, July the 17th.


Attendees

Regrets

DMCCB Meeting Goals

      • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-593 - Getting issue details... STATUS Planned end: Jun/14/2019

RFC-605 - Getting issue details... STATUS Planned end: Jun/26/2019

RFC-611 - Getting issue details... STATUS Planned end: Jul/15/2019

RFC-612 - Getting issue details... STATUS Planned end: Jul/15/2019

RFC-613 - Getting issue details... STATUS Planned end: Jul/12/2019

RFC-614 - Getting issue details... STATUS Planned end: Jul/13/2019

RFC-615 - Getting issue details... STATUS Planned end: Jul/18/2019

RFC-617 - Getting issue details... STATUS Planned end: Aug/02/2019

RFC-618 - Getting issue details... STATUS Planned end: Jul/23/2019

RFC-619 - Getting issue details... STATUS Planned end: Jul/19/2019

  • RFC-593: end date moved to July 31
  • RFC-605: seems fine, but RLupton would like this to be fixed somewhere else
    • Technote could be written but no time for it
    • To keep on hold: to move the end date one week
  • RFC-617: for the CCB point of view it is fine. Add a comment.
  • RFC-611: 
    • section 3 to be renamed Verification Control
    • Ready to be adopted
  • RFC-612:
  • RFC-613: LDM-152
    • so far no problems from the DMCCB, the 
  • RFC-614: LDM-148
    • new product tree and some minor changes
    • OK
  • RFC-615: LDM-144
    • Kian-Tat Lim has a look and changes seems reasonable, some concerns about costs increasing
    • Unknown User (mbutler) the model used to do this estimation is quite old, and it should be reviewed
    • Kian-Tat Lim suggests not to modify the baseline, but to submit the document to the review as a draft.
    • DM-CCB decided not to Board Recommend the RFC and review the document trying to reduce the costs.
  • RFC-619: LDM-672
Board Recommended RFCs

RFC-606 - Getting issue details... STATUS Planned end: Jul/01/2019


Adopted but not implemented LDM RFCs (only document RFCs)

None


Proposed RFCs

(to review, do not require DMCCB approval)

RFC-616 - Getting issue details... STATUS Planned end: Jul/19/2019

RFC-585 - Getting issue details... STATUS Planned end: Jun/14/2019

  • no comments.

Adopted RFCs without Triggering issues

(to create implementing DM issues)

RFC-607 - Getting issue details... STATUS

RFC-607 has a triggered ticket as of shortly after this page being published. (Thanks, Tim Jenness )

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

RFC-599 - Getting issue details... STATUS



RFCs adopted since last CCB

(to review, no action required)

RFC-608 - Getting issue details... STATUS

RFC-609 - Getting issue details... STATUS

RFC-610 - Getting issue details... STATUS


RFCs implemented since last CCB

(to review, no action required)

RFC-610 - Getting issue details... STATUS

RFC-602 - Getting issue details... STATUS

RFC-604 - Getting issue details... STATUS

RFC-608 - Getting issue details... STATUS

RFC-609 - Getting issue details... STATUS


Changes to the planned releases
  • 18.0.0 Release status
    • Release completed.
    • DM-19147 - Getting issue details... STATUS
  • Next Releases:
    • proposed 18.1.0 as per RFC-618
  • RFC-618: DMCCB is fine
    • Unknown User (gcomoretto)to open a Jira issue for the 18.1.0 release and comment on the RFC-618, release to be available in 2 weeks

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. DM-2918 - Getting issue details... STATUS
  2. DM-1163 - Getting issue details... STATUS
  3. DM-1248 - Getting issue details... STATUS
  4. DM-1643 - Getting issue details... STATUS
  5. DM-5176 - Getting issue details... STATUS
  6. DM-5184 - Getting issue details... STATUS
  7. DM-954 - Getting issue details... STATUS
  8. DM-1169 - Getting issue details... STATUS
  9. DM-4048 - Getting issue details... STATUS
  10. DM-4047 - Getting issue details... STATUS

3957 unresolved issues (3937 on July the 10th)

  • DM-2918 still valid. Bumped ticket.
  • DM-5184 now in review done.
Open Actions

AOB
Next DM-CCB 
July the 24


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)