Location
| Browser | Room System | Phone Dial-in |
|---|
| https://bluejeans.com/761546516/ | - Dial: 199.48.152.152 or bjn.vc
- 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, December the 2nd.
Attendees
Regrets
DMCCB Meeting Goals
- See DMCCB responsibilities listed in LDM-294 section 7.4
DMCCB Additional Resources
Discussion Items
| Item | Description | CCB Notes |
|---|
Flagged RFCs (To be approved by the DMCCB) | -
RFC-741
-
Getting issue details...
STATUS
Planned end: Nov/25/2020
-
RFC-737
-
Getting issue details...
STATUS
Planned end: Nov/04/2020
-
RFC-699
-
Getting issue details...
STATUS
Planned end: Nov/30/2020
-
RFC-695
-
Getting issue details...
STATUS
Planned end: Nov/30/2020
| - RFC-741: still discussion ongoing
- RFC-737: DMCCB agreed to Board Recommend it
- RFC-699: this seems to be more Gen2 focus, need to be refocused to be oriented to Gen3 backward compatibility
- Still waiting from Elay for some comment
- Maybe somebody else should be asked to comment: JimB?
- The implementation should be blocked by RFC-741
- Jim BoschRFC-699: to write a text for the developer guide
- RFC-695: Leanne to move forward the end date
|
| Board Recommended RFCs |
|
|
| Adopted but not implemented LDM RFCs (only document RFCs) |
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-742
-
Getting issue details...
STATUS
Planned end: Nov/26/2020
-
RFC-727
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Jun/7/2021
| - RFC-742: not a DMCCB problem
- RFC-727: should already be implemented
|
Adopted RFCs without Triggering issues (to create implementing DM issues) | -
RFC-709
-
Getting issue details...
STATUS
-
RFC-726
-
Getting issue details...
STATUS
- From DMCCB71: Crish should be working on opening related tickets.
-
RFC-733
-
Getting issue details...
STATUS
| - RFC-733 should already be done... just needs to be linked with the ticket
- RFC-726:
- The assignee is still working on the design and the RFC is still not ready yet.
- Jim Bosch to add a comment and possible an implementation ticket
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') |
|
|
RFCs adopted since the last DMCCB (to review, no action required) | -
RFC-733
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since the last DMCCB (to review, no action required) | -
RFC-312
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned Release 21.0.0
-
DM-22815
-
Getting issue details...
STATUS
- Release candidate 1 ready
- Working on Release Note and Characterization Report
- End of November deadline not realistic anymore, but the release could be finalized in the forthcoming days.
- CLO status and discussion:
| - waiting for Characterization Report
- Release Note should be almost there but need to check the status of the publication of pipelines.lsst.io with Jonatan
- Could be finalized this week, or at latest at the beginning of next week
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| -
DM-10545
-
Getting issue details...
STATUS
-
DM-10593
-
Getting issue details...
STATUS
-
DM-2041
-
Getting issue details...
STATUS
-
DM-2117
-
Getting issue details...
STATUS
-
DM-2059
-
Getting issue details...
STATUS
-
DM-4268
-
Getting issue details...
STATUS
-
DM-218
-
Getting issue details...
STATUS
-
DM-4700
-
Getting issue details...
STATUS
-
DM-2874
-
Getting issue details...
STATUS
-
DM-2086
-
Getting issue details...
STATUS
4002 unresolved issues (3946 on November the 25th) | - DM-2059, DM-4700, DM-218, DM-10593: still relevant, low priority
|
| Open Actions |
|
|
| AOB | | |
| Next DM-CCB | December 9th |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions