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, April 28th 2021.


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

  • RFC-771 - Getting issue details... STATUS Planned end: Apr/21/2021

  • RFC-775 - Getting issue details... STATUS Planned end: Apr/28/2021
  • RFC-777 - Getting issue details... STATUS Planned end: May/7/2021

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)

  • RFC-638 - Getting issue details... STATUS Planned end: Jun/7/2021

  • RFC-774 - Getting issue details... STATUS  Planned end: Apr/15/2021
  • RFC-778 - Getting issue details... STATUS  Planned end: Apr/30/2021
  • RFC-776 - Getting issue details... STATUS  Planned end: May/7/2021


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)

  • RFC-760 - Getting issue details... STATUS
  • RFC-765 - Getting issue details... STATUS

RFCs implemented (or withdrawn) since the last DMCCB

(to review, no action required)






Releases

  • Planned
  • Changes to the release schedule
  • Next planned Release 22.0.0
    • May 2021 / not linked to DP0.2 version
    • Activity has started.
    • Release notes ticket:  DM-29602 - Getting issue details... STATUS
  • Patch releases
    • None requested at the moment
  • Work on this has begun.
    • YA is collecting release notes
    • JC is writing the characterization report
  • YA finally executed the test plan for the fall-2020 release:
    • went fine but filed tickets for a couple docs improvements:
      • commented on ticket  DM-28988 - Getting issue details... STATUS  to add instructions on how to find the right shared stack.
      • quick update to pipelines_check README:  DM-29904 - Getting issue details... STATUS
      • and v21.0.0.rc1 but no v21.0.0 in shared stack at time of writing. 

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)
  1. DM-10915 - Getting issue details... STATUS
  2. DM-10940 - Getting issue details... STATUS
  3. DM-10951 - Getting issue details... STATUS
  4. DM-10791 - Getting issue details... STATUS
  5. DM-10817 - Getting issue details... STATUS
  6. DM-10900 - Getting issue details... STATUS
  7. DM-10987 - Getting issue details... STATUS
  8. DM-7922 - Getting issue details... STATUS
  9. DM-10994 - Getting issue details... STATUS
  10. DM-5824 - Getting issue details... 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

Key Summary
Loading...
Refresh

Pending Proposed RFCs

Key Summary
Loading...
Refresh

Oldest issues

Key Summary
Loading...
Refresh

Meeting outcome


Pending DMCCB Actions

Task report

Looking good, no incomplete tasks.