Location

Zoom link available on Slack channel.

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesdays.


Attendees: 

Wil O'Mullane Tim Jenness 

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
  • RFC-863 - Getting issue details... STATUS
  • RFC-946 - Getting issue details... STATUS
  • RFC-956 - Getting issue details... STATUS
  • RFC-957 - Getting issue details... STATUS
  • RFC-964 - Getting issue details... STATUS
  • RFC-958 - Getting issue details... STATUS


958 remains contentious .. Colin would like to fail but not the entire  processing. Currently not possible entire coadd would fail if we fail one isr . Could write log.error but allow the system to run - Jim log is minimum - we need to accept problems and too many fails should fail.. How do we scale up to - we dont have a way to mark a failure as acceptable .. 

Colin offers realtime discussion - get time and people ..

Kafka producer 964 - KT made comment - but no reply .

957 - still KT has to read and 956

 Board Recommended RFCs

  • RFC-938 - Getting issue details... STATUS
  • RFC-911 - Getting issue details... STATUS
  • RFC-959 - Getting issue details... STATUS
  • RFC-960 - Getting issue details... STATUS
  • RFC-965 - Getting issue details... STATUS
  • RFC-828 - Getting issue details... STATUS

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-880 - Getting issue details... STATUS
  • RFC-902 - Getting issue details... STATUS
  • RFC-907 - Getting issue details... STATUS
  • RFC-920 - Getting issue details... STATUS
  • RFC-934 - Getting issue details... STATUS
  • RFC-966 - Getting issue details... STATUS



 Adopted RFCs without Triggering issues

(to create implementing DM issues)



Open LCRs


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

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

RFCs adopted since the last DMCCB

(to review, no action required)

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


RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)






Releases

  • Planned
  • Changes to the release schedule


Tim did resource backport to 25 - Mattias did 4 backports for 26 will get on to 25 next,

Scarlet bakcport was not tricky

26 - chareterization report ? Are we ready ? need bakc ports and RC2 - RC2 shoudl have happened (backport should have been ok) close

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-22288 - Getting issue details... STATUS
  2. DM-22434 - Getting issue details... STATUS
  3. DM-12655 - Getting issue details... STATUS
  4. DM-16763 - Getting issue details... STATUS
  5. DM-15550 - Getting issue details... STATUS
  6. DM-21162 - Getting issue details... STATUS
  7. DM-19661 - Getting issue details... STATUS
  8. DM-20968 - Getting issue details... STATUS
  9. DM-22562 - Getting issue details... STATUS
  10. DM-23018 - Getting issue details... STATUS


Unresolved issues: 4497


Open Actions


pypi could do pipelines version .. want us to stop using tokens

should improvements be pushed up to DM packaes

CST which account should be used ?

Tim will write somethign he needs to tell leanne


AOB 


Merlin wanted to hear about 3rd part contrib code ?

Next DM-CCB 

2023-10-25



Pending Flagged RFCs

Key Summary
Loading...
Refresh

Pending Proposed RFCs

Key Summary
Loading...
Refresh

Oldest issues

Key Summary
Loading...
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
25 Apr 2024Frossie EconomouDMCCB#197 (2024 - 04 - 14)