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.05 to 09.35 PT, Wednesday, December the 18th.
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: Dec/16/2019
| - RFC-620
- Mario added some updates
- End date to be moved to mid-January
|
| 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: Dec/15/2019
-
RFC-648
-
Getting issue details...
STATUS
Planned end: Dec/13/2019
-
RFC-651
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-652
-
Getting issue details...
STATUS
Planned end: Jan/22/2020
-
RFC-653
-
Getting issue details...
STATUS
Planned end: Jan/08/2020
| - RFC-638 to update the planned end date to end-January
- RFC-648, on KT table
- RFC-651 and RFC-652
- RFC-653 it should be approved by KT
- it seems that the proposal is not clear
|
Adopted RFCs without Triggering issues (to create implementing DM issues) |
|
|
Adopted RFCs with all triggered work COMPLETED (to set status as 'IMPLEMENTED') | -
RFC-243
-
Getting issue details...
STATUS
|
|
RFCs adopted since last CCB (to review, no action required) | -
RFC-645
-
Getting issue details...
STATUS
-
RFC-647
-
Getting issue details...
STATUS
|
|
RFCs implemented (or withdraw) since last CCB (to review, no action required) | -
RFC-649
-
Getting issue details...
STATUS
|
|
Releases - Planned
- Changes to the release schedule
| - Next planned major release 20.0.0
| - Potential path 19.0.1
- there is a documentation fix that may be required.
- it is not clear if this is a critical fix or not?
- The ticket is: DM-22027
- Leanne Guy the releases are for the community, rebuilding the reference catalog is for the developer, and this can be done on the weekly.
- Tim Jenness suggest that a community post may address the problem until the next major release
- The documentation is built from the tag.
- Kian-Tat Lim suggest to create a branch and cherry-pick docs from that branch.
- Unknown User (gcomoretto) to investigate with Jonathan how easy is to get this pipelines.lsst.io updated using a 19.0.x branch, in order to have DM-22027 clarified on top of 19.0.0 release
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity -
DM-5984
-
Getting issue details...
STATUS
-
DM-5985
-
Getting issue details...
STATUS
-
DM-6052
-
Getting issue details...
STATUS
-
DM-6053
-
Getting issue details...
STATUS
-
DM-6570
-
Getting issue details...
STATUS
-
DM-2879
-
Getting issue details...
STATUS
-
DM-5787
-
Getting issue details...
STATUS
-
DM-6496
-
Getting issue details...
STATUS
-
DM-6584
-
Getting issue details...
STATUS
-
DM-5724
-
Getting issue details...
STATUS
3858 unresolved issues (3880 on November the 20th) | - DM-5984 → Unknown User (npease) to verify and comment if this is still relevant.
- DM-5985, DM-6052, DM-6053 → Still relevant; likely to be swept up in ongoing k8s-ification of Qserv (via k8s secret and configuration cleanup.)
- DM-2879, DM-5724 → Won't Fix.
- DM-6584 → Done.
- DM-5787, DM-6496 → Keep open for the convenience of the HSC team. Will not be worked on project.
- DM-6570 → Still seems valid; low priority.
|
| Open Actions |
|
|
| AOB |
|
|
| Next DM-CCB |
| January 8th, 2020. |
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions