Skip to end of metadata
Go to start of metadata

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, June the 12th.


Attendees

Regrets

DMCCB Meeting Goals

      • See DMCCB responsibilities listed in LDM-294 section 7.4

DMCCB Additional Resources

Discussion Items

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-601 - Getting issue details... STATUS Planned end: Jun/08/2019

RFC-593 - Getting issue details... STATUS Planned end: Jun/14/2019

Board Recommended RFCs

None


Adopted but not implemented LDM RFCs (only document RFCs)

None


Proposed RFCs

(to review, do not require DMCCB approval)

RFC-600 - Getting issue details... STATUS Planned end: Jun/29/2019

RFC-585 - Getting issue details... STATUS Planned end: Jun/14/2019

  • RFC-600 is on the SST agenda for this week 

Adopted RFCs without Triggering issues

(to create implementing DM issues)

RFC-599 - Getting issue details... STATUS

  • Tim Jenness already contacted the assignee to add triggering issues.

Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

None



RFCs adopted since last CCB

(to review, no action required)

RFC-581 - Getting issue details... STATUS

RFC-599 - Getting issue details... STATUS

RFC-598 - Getting issue details... STATUS



RFCs implemented since last CCB

(to review, no action required)

RFC-577 - Getting issue details... STATUS

RFC-594 - Getting issue details... STATUS

RFC-597 - Getting issue details... STATUS



Changes to the planned releases
  • 18.0 Release status
    • First Release Candidate based on w_2019_23
  • DM-19147 - Getting issue details... STATUS
  • ready to go with v18.0.0.rc1

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity

  1. DM-1594 - Getting issue details... STATUS
  2. DM-1546 - Getting issue details... STATUS
  3. DM-1426 - Getting issue details... STATUS
  4. DM-1602 - Getting issue details... STATUS
  5. DM-4942 - Getting issue details... STATUS
  6. DM-867 - Getting issue details... STATUS
  7. DM-4005 - Getting issue details... STATUS
  8. DM-4973 - Getting issue details... STATUS
  9. DM-5009 - Getting issue details... STATUS
  10. DM-5045 - Getting issue details... STATUS

4055 unresolved issues (4061 on May the 21st)

Open Actions

AOB
  • Tim Jenness : a couple of more LDMs on requirements almost ready  for RFC:
    • LDM-635: need more text, plus requirements are just copies from LSE-61 reqs. Do we need more time to complete, or just go with what we have? Everybody seems OK to go with what we have.
    • LDM-636: already docugenerated and available in lsst.io
    • they should be available for next week.


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
Gabriele ComorettoDMCCB#60 (2020 - 08 - 05)
Kian-Tat LimDMCCB#60 (2020 - 08 - 05)
  • Tim Jenness  to write a policy on how external code written by DM shall be handled.
Tim JennessDMCCB#51 (2020 - 05 - 27)
  • John Swinbankwrite a text to clarify when an RFC need to flag (DM-25191)
John SwinbankDMCCB#51 (2020 - 05 - 27)