Data Management
Space shortcuts
Page tree
Skip to end of metadata
  • Created by Unknown User (gcomoretto), last modified on Jun 03, 2020
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, June the3rd.


Attendees

Regrets

  • TBD

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-701 - Getting issue details... STATUS Planned end: Jun/09/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Jun/03/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Jul/31/2020
  • RFC-701: just new still discussions ongoing
    • no actions to be taken today
  • RFC-699: discussion converging, it should be just up to Tim Jenness
    • postponed to next week
  • RFC-695: still plenty of time to discuss it (end of July)
    • Leanne Guy to check if the end date of RFC-695 is driven by some specific factor  – it was an arbitrary choice meant to indicate that it was not urgent on the 2-week timescale. I will review the science driver and update the ticket.
Board Recommended RFCs


Adopted but not implemented LDM RFCs (only document RFCs)

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-700 - Getting issue details... STATUS Planned end: Jun/12/2020
  • RFC-698 - Getting issue details... STATUS Planned end: Jun/24/2020
  • RFC-697 - Getting issue details... STATUS Planned end: May/29/2020
  • RFC-680 - Getting issue details... STATUS Planned end: Apr/01/2020
  • RFC-652 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-651 - Getting issue details... STATUS Planned end: Jan/22/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021
  • RFC-700 Flagged
  • RFC-698 KT
  • RFC-697 transparent for CCB
  • RFC-680 should just be adopted
  • RFC-652
    • Flagged
  • RFC-651
    • Flagged
  • RFC-638, long term discussion

Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

  • RFC-333 - Getting issue details... STATUS
  • RFC-640 - Getting issue details... STATUS
  • RFC-686 - Getting issue details... STATUS

RFCs adopted since last CCB

(to review, no action required)

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

RFCs implemented (or withdraw) since last CCB

(to review, no action required)

  • RFC-689 - Getting issue details... STATUS
  • RFC-693 - Getting issue details... STATUS
  • RFC-31 - Getting issue details... STATUS


Releases

  • Planned
  • Changes to the release schedule
  • The problems found on w22 should come out on the weekly assessments
  • Leanne Guy Why those problems are not highlighted by unit and regression testing?
    • The reference date is changing and therefore is difficult to catch these type of problems
    • Large datasets are required
  • 3 issues blocking the release candidate
  • John Swinbank  can do the backport
  • Kian-Tat Lim : has something been added sine w22?
    • the default answer if no
  • DMCCB decided to go with w22 and do backport.

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity.

  1. DM-7102 - Getting issue details... STATUS
  2. DM-8958 - Getting issue details... STATUS
  3. DM-8974 - Getting issue details... STATUS
  4. DM-8987 - Getting issue details... STATUS
  5. DM-7257 - Getting issue details... STATUS
  6. DM-7806 - Getting issue details... STATUS
  7. DM-8998 - Getting issue details... STATUS
  8. DM-8988 - Getting issue details... STATUS
  9. DM-2517 - Getting issue details... STATUS
  10. DM-8655 - Getting issue details... STATUS

3950 unresolved issues (3928 on May the27th)

  • DM-7102: Still relevant (probably), added comment.
  • DM-8958: Still relevant, added comment.
  • 8974: Sill relevant.  Attached to ongoing secondary index epic.
  • DM-8998: Still relevant (probably), reassigned, added comment.
  • DM-2517: And I nixed the RFC, too.
Open Actions
  • everybody to look at DM-25191
  • policy on external code: a proposal available from KT
AOB
  • issue list to backport in
    • DM-25221
Next DM-CCB June the 10th


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)
21 Jun 2023Kian-Tat LimDMCCB#165 (2023 - 06 - 07)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
 Tim JennessDMCCB#51 (2020 - 05 - 27)



  • No labels