Skip to end of metadata
Go to start of metadata

Location

Zoom link available on Slack channel.

(Back to the DMCCB page)

Time

From 9.00 to 09.30 PT, Wednesdays.


Attendees

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 Planned end: Apr/21/2021

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

771 - Awaiting Gregory Dubois-Felsmann 

826cfitsio pinning timeline - could be1 week.needs 2.0. Did build with python 3.10, no objections to pushing ahead


Board Recommended RFCs
  • RFC-822 - Getting issue details... STATUS

Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-819 - Getting issue details... STATUS
  • RFC-823 - Getting issue details... STATUS
  • RFC-825 - Getting issue details... STATUS



 Adopted RFCs without Triggering issues

(to create implementing DM issues)



Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')



RFCs adopted since the last DMCCB

(to review, no action required)

  • RFC-818 - Getting issue details... STATUS
  • RFC-813 - Getting issue details... STATUS
  • RFC-824 - Getting issue details... STATUS


RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)

  • RFC-820 - Getting issue details... STATUS
  • RFC-321 - Getting issue details... STATUS





Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 23.0.1:
    • paperwork ticket:  DM-33516
      • Kian-Tat Lim, Do you think it is worth adding the lsstinstall instructions?


YA: We ran 5 tracts with rc2 and found DM-33596. Fix reviewed and Jenkins'ed. Want an rc3?
do we need an rc3. no reason not to do it ready to go .. does not fix s3 timeout .. on 5 tract test - sub 1% hit from this. Can live with it for now. Overlapping tracts may be a problem. So we go with rc3 .. for now.

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-14249 - Getting issue details... STATUS
  2. DM-10402 - Getting issue details... STATUS
  3. DM-10781 - Getting issue details... STATUS
  4. DM-14303 - Getting issue details... STATUS
  5. DM-14326 - Getting issue details... STATUS
  6. DM-14324 - Getting issue details... STATUS
  7. DM-2181 - Getting issue details... STATUS
  8. DM-14169 - Getting issue details... STATUS
  9. DM-9396 - Getting issue details... STATUS
  10. DM-14524 - Getting issue details... STATUS

Unresolved issues: 4248


Open Actions

AOB
Next week no CCB

Dominique Boutigny reports that he is not concerned about removing gen2 support from obs_cfht. 

DM-33523 - Getting issue details... STATUS
Next DM-CCB February 23rd 2022


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
  • 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)