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, October the 29st.
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-732
-
Getting issue details...
STATUS
Planned end Oct/28/2020
-
RFC-699
-
Getting issue details...
STATUS
Planned end: Oct/30/2020
-
RFC-695
-
Getting issue details...
STATUS
Planned end: Oct/30/2020
| - RFC-732: No problems from KT
- to board recommend and finish the update
- RFC-699 and RFC-695 we are getting close to the due date
- Leanne suggests moving forward RFC-695 another month
- RFC-699:
- Still waiting for some text from Elay. Tim said that this should be Architecture responsibility or Jim
|
| Board Recommended RFCs | -
RFC-733
-
Getting issue details...
STATUS
-
RFC-709
-
Getting issue details...
STATUS
| - RFC-709 can be adopted now
- so the LCR can be files and LSE-61 changed
- RFC-733 is blocked until the next release is done
|
| Adopted but not implemented LDM RFCs (only document RFCs) | -
RFC-710
-
Getting issue details...
STATUS
- LCR-2643 should be approved now, the RFC can move forward
|
|
Proposed RFCs (to review, do not require DMCCB approval) | -
RFC-727
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
-
RFC-726
-
Getting issue details...
STATUS
Planned end: Sep/30/2020
-
RFC-638
-
Getting issue details...
STATUS
Planned end: Jun/7/2021
|
|
Adopted RFCs without Triggering issues (to create implementing DM issues) | -
RFC-710
-
Getting issue details...
STATUS
(waiting for LCR-2643)
-
RFC-723
-
Getting issue details...
STATUS
|
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | -
RFC-703
-
Getting issue details...
STATUS
|
|
RFCs adopted since the last DMCCB (to review, no action required) | -
RFC-723
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since the last DMCCB (to review, no action required) | -
RFC-688
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned Release 21.0.0
-
DM-22815
-
Getting issue details...
STATUS
- Tentative schedule:
- start: November 2nd
- release available: November 20th
- Pending blocking issues:
-
DM-22578
-
Getting issue details...
STATUS
-
DM-22814
-
Getting issue details...
STATUS
-
DM-23374
-
Getting issue details...
STATUS
-
DM-24331
-
Getting issue details...
STATUS
-
DM-22114
-
Getting issue details...
STATUS
- CLO status and discussion:
| - DM-23374 should be done by the end of the day
- The other should be under control by Yusra
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| -
DM-5570
-
Getting issue details...
STATUS
-
DM-8682
-
Getting issue details...
STATUS
-
DM-10157
-
Getting issue details...
STATUS
-
DM-10162
-
Getting issue details...
STATUS
-
DM-10163
-
Getting issue details...
STATUS
-
DM-5174
-
Getting issue details...
STATUS
-
DM-5789
-
Getting issue details...
STATUS
-
DM-10198
-
Getting issue details...
STATUS
-
DM-10245
-
Getting issue details...
STATUS
-
DM-10260
-
Getting issue details...
STATUS
3927 unresolved issues (3938 on October the 21st) | - DM-5570 invalid
- other issues have been commented on or addressed.
|
| Open Actions |
| Change action on John to Yusra, about RFC-699. The RFC will be in |
| AOB | | Robert Lupton asked informally (in #dm-camelot and #dm-ccb slack channels) to do a path on 18.0 release: - "Over on the PFS project, we've found that sconsUtils doesn't support debian. We are using v18 as a base (we'll go to Rubin-latest once gen3 is stable), so we can't just submit a patch to sconsUtils master/main.
PFS can handle this in their world, or we could ask for a v18 patch release. What would Rubin like them to do? "
DMCCB considered the proposal and decided that a patch release based on 18.0.0 major release is not justified this time. It has been considered also that we now use conda compilers for all builds. |
| Next DM-CCB | November 4th. |
|
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions