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, September the 4st.
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-620
-
Getting issue details...
STATUS
Planned end: Sep/09/2019
RFC-626
-
Getting issue details...
STATUS
Planned end: Aug/28/2019 |
- RFC-626: Board Recommended
- implementing tickets to be related to the release 19.0.0 issue
- RFC-620: Mario is not expecting to announce until October
|
Board Recommended RFCs | | |
Adopted but not implemented LDM RFCs (only document RFCs) | |
|
Proposed RFCs (to review, do not require DMCCB approval) |
RFC-624
-
Getting issue details...
STATUS
Planned end: Aug/30/2019 | This is an API change, and DM-CCB still did not pronounce. DMCCB#25 (2019 - 09 - 04) asked if the CCB should be involved or let it proceed, without flagging: - DM-CCB agreed no need to flag it.
|
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 last CCB (to review, no action required) |
RFC-617
-
Getting issue details...
STATUS
RFC-625
-
Getting issue details...
STATUS
RFC-593
-
Getting issue details...
STATUS
RFC-623
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) |
RFC-188
-
Getting issue details...
STATUS
RFC-617
-
Getting issue details...
STATUS
RFC-599
-
Getting issue details...
STATUS
|
|
Changes to the planned releases | - Next Major release 19.0.0
|
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity -
DM-3381
-
Getting issue details...
STATUS
-
DM-4209
-
Getting issue details...
STATUS
-
DM-4201
-
Getting issue details...
STATUS
-
DM-5365
-
Getting issue details...
STATUS
-
DM-4541
-
Getting issue details...
STATUS
-
DM-4549
-
Getting issue details...
STATUS
-
DM-866
-
Getting issue details...
STATUS
-
DM-3445
-
Getting issue details...
STATUS
-
DM-4077
-
Getting issue details...
STATUS
-
DM-2912
-
Getting issue details...
STATUS
3912 unresolved issues (4000 on August the 21st) | John Swinbank comments: - DM-4201 seems legit, but low priority.
- Ditto DM-4209.
- Ditto DM-3381.
- Tim has already commented on DM-4541, so it's not an issue for this DM-CCB meeting. However, I suggest we'd want to take stock of our priorities before we were to go ahead with this work.
- DM-4549 has a recent comment.
- DM-3445 is the subject of periodic outbursts of discussion (e.g. https://community.lsst.org/t/reference-catalogs-camfluxes-and-colorterms/3578). We should think about a redesign, but we should not simply dive in and implement that ticket without further thought.
|
Open Actions |
|
|
AOB |
|
|
Next DM-CCB |
| Sept. 11th. |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions