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
  • RFC-863 - Getting issue details... STATUS
  • RFC-894 - Getting issue details... STATUS
  • RFC-901 - Getting issue details... STATUS




894 with Parejko

901 - Jim allowing post AAS time to look at it.

Board Recommended RFCs

  • RFC-888 - Getting issue details... STATUS
  • RFC-828 - Getting issue details... STATUS
  • RFC-895 - Getting issue details... STATUS


Proposed RFCs

(to review, do not require DMCCB approval)

  • RFC-880 - Getting issue details... STATUS
  • RFC-884 - Getting issue details... STATUS

884 - Leanne will chase a bit

 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-900 - Getting issue details... STATUS


RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)






Releases

  • Planned
  • Changes to the release schedule


  • 23.03 blocked on Colin's ticket  DM-37232 - Getting issue details... STATUS
  • V24 back ports progressing but getting difficult because of drp_tasks which does not exist in v24. Agree to put the new task in pipe_tasks in the v24.1 release and announce that in future it will be in drp_tasks.
  • V25 0 release candidate
    • characterization report ticket made but not complete.
  • Tags missing on ci packages and rc2_subset tutorial package. How do we automate those?
    • Mathias known feature. Needs to be manual tagged or retagged. Need to do a better audit on the ci packages. Can write a short code to do this.
    • rc2_subset is never built.
    • Does it have to do in lsst_w - perhaps it can be built and included.
    • ci_cpp not yet getting tags. Added correct team and will see if weekly tag appears tonight.
    • Mathias now understands these have not been tagged at all.
    • Tutorial needs to be updated to indicate people should clone the release tag and not main.
    • how does ci_hsc get a weekly tag - the weekly build is run of lsst_distrib and lsst_ci then git tags eups products all dm not dm_external, but dm_auxilaries - perhaps ci has the wrong team ci_hsc is auxiliary .. ci_cpp and rc2_subset should have this team added.. it is on ci_cpp but it may have been done last week after build.  rc2_subset is not correct and is in lsst-dm org  (should be added to Mathias list - manually tag retrospectiviely) ci_builder also not tagged and also in lsst-dm org on GitHub so is not tagged.

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-5578 - Getting issue details... STATUS
  2. DM-19224 - Getting issue details... STATUS
  3. DM-18695 - Getting issue details... STATUS
  4. DM-2876 - Getting issue details... STATUS
  5. DM-3201 - Getting issue details... STATUS
  6. DM-19252 - Getting issue details... STATUS
  7. DM-19294 - Getting issue details... STATUS
  8. DM-917 - Getting issue details... STATUS
  9. DM-1898 - Getting issue details... STATUS
  10. DM-16247 - Getting issue details... STATUS


Unresolved issues: 4193

(we are now encountering old T&S tickets)


Open Actions



AOB 



Next DM-CCB 2023-02-01


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  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)