Location
| Browser | Room System | Phone Dial-in |
|---|---|---|
| https://bluejeans.com/761546516/ |
| Dial-in numbers:
Meeting ID: 761546516 |
(Back to the DMCCB page)
Time
From 9.00 to 09.30 PT, Wednesday, April 28th 2021.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
DMCCB Additional Resources
- #dm-ccb slack channel
Discussion Items
| Item | Description | CCB Notes |
|---|---|---|
Flagged RFCs (To be approved by the DMCCB) | 769 - wait another week to deal with Bob's comments 775 - heated debate .. need real example - push date another week to have some conversations (jim) - AP does not run in DRP, no alerts its mainly diffim, 777 - not run at scale .. but uuid is performat enough (sqllite is slower)- do we have tools to convert .. Process question should this RFC be before work starts, this depends on how traumatic the changes are is the API, is there backward compatibility? Is migrateable ? In this case the same code is used to read the old and new repos. CI-HSC gen3 is using new scheme... if users will notice file RFC .. if not file when the work is on. Jim points out users of released versions may notice (i.e. inability to use new repo if using last stable). Need this for DP0.2 - questionn if this should be cherry picked into release 22 of pipeline. UUID was in weekly 16. | |
| Board Recommended RFCs | ||
| Adopted but not implemented LDM RFCs (only document RFCs) | ||
Proposed RFCs (to review, do not require DMCCB approval) | 774 - title incorrect. It's not going in distrib but into lsst_ci 778 - blocked by 777 - not really an issue for CCB. Discussion came down on including collection in UUID5. | |
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) | ||
RFCs implemented (or withdrawn) since the last DMCCB (to review, no action required) | ||
Releases
|
|
|
Monitor Jira issues status:
|
Unresolved issues: 3974 | 7922 - will wait for the v22 release and then close all old gen2 tickets as won't fix. |
| Open Actions | ||
| AOB | ||
| Next DM-CCB | May 5th |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
| Description | Due date | Assignee | Task appears on |
|---|---|---|---|
| Tim Jenness | DMCCB#51 (2020 - 05 - 27) |