Data Management
Space shortcuts
Page tree
Skip to end of metadata
  • Created by Unknown User (gcomoretto), last modified on Oct 28, 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, October the 29st.


Attendees

Regrets

  • TBD

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-732 - Getting issue details... STATUS Planned end Oct/28/2020
  • RFC-699 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-695 - Getting issue details... STATUS Planned end: Oct/30/2020
  • RFC-732: No problems from KT
    • to board recommend and finish the update
  • RFC-699 and RFC-695 we are getting close to the due date
    • Leanne suggests moving forward RFC-695 another month
    • RFC-699:
      • Still waiting for some text from Elay. Tim said that this should be Architecture responsibility or Jim
Board Recommended RFCs
  • RFC-733 - Getting issue details... STATUS
  • RFC-709 - Getting issue details... STATUS
  • RFC-709 can be adopted now
    • so the LCR can be files and LSE-61 changed
  • RFC-733 is blocked until the next release is done
Adopted but not implemented LDM RFCs (only document RFCs)
  • RFC-710 - Getting issue details... STATUS
    • LCR-2643 should be approved now, the RFC can move forward

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-727 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-726 - Getting issue details... STATUS Planned end: Sep/30/2020
  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021

Adopted RFCs without Triggering issues

(to create implementing DM issues)

  • RFC-710 - Getting issue details... STATUS (waiting for LCR-2643)
  • RFC-723 - Getting issue details... STATUS

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

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

RFCs adopted since the last DMCCB

(to review, no action required)

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

RFCs implemented (or withdraw) since the last DMCCB

(to review, no action required)

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


Releases

  • Planned
  • Changes to the release schedule
  • DM-23374 should be done by the end of the day
  • The other should be under control by Yusra

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-5570 - Getting issue details... STATUS
  2. DM-8682 - Getting issue details... STATUS
  3. DM-10157 - Getting issue details... STATUS
  4. DM-10162 - Getting issue details... STATUS
  5. DM-10163 - Getting issue details... STATUS
  6. DM-5174 - Getting issue details... STATUS
  7. DM-5789 - Getting issue details... STATUS
  8. DM-10198 - Getting issue details... STATUS
  9. DM-10245 - Getting issue details... STATUS
  10. DM-10260 - Getting issue details... STATUS

3927 unresolved issues (3938 on October the 21st)

  • DM-5570 invalid
  • other issues have been commented on or addressed.
Open Actions
Change action on John to Yusra, about RFC-699. The RFC will be in 
AOB


Robert Lupton asked informally (in #dm-camelot and #dm-ccb slack channels) to do a path on 18.0 release:

  • "Over on the PFS project, we've found that sconsUtils doesn't support debian.   We are using v18 as a base (we'll go to Rubin-latest once gen3 is stable), so we can't just submit a patch to sconsUtils master/main.
    PFS can handle this in their world, or we could ask for a v18 patch release.  What would Rubin like them to do? "

DMCCB considered the proposal and decided that a patch release based on 18.0.0 major release is not justified this time. It has been considered also that we now use conda compilers for all builds.

Next DM-CCB November 4th.


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)



  • No labels