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 11th.
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 Board Recommended RFCs
RFC-645
-
Getting issue details...
STATUS
Planned end: Nov/13/2019
RFC-647
-
Getting issue details...
STATUS
Planned end: Dec/03/2019 RFC-645 RFC-647Now that the release is done, conda env can be updated 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-649
-
Getting issue details...
STATUS
Planned end: Dec/20/2019
RFC-650
-
Getting issue details...
STATUS
Planned end: Dec/13/2019 John Swinbank no changes to code standards shall be considered unless they are critical
Colin Slater we should make clear that the decision is on topics like RFC-649 and RFC-650 are on the CCB and not the single developer
RFC-649 flagged
John Swinbank to answer on RFC-649: not a valid proposal for DM, but can be implemented in T&S (DM may reconsider it afterwords)Kian-Tat Lim to assess RFC-650Adopted 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)
RFCs implemented (or withdraw) since last CCB
(to review, no action required)
RFC-635
-
Getting issue details...
STATUS
Releases
Planned Changes to the release schedule Science Pipelines version 19.0.0 was officially released on December the 6th. Next planned major release 20.0.0 John Swinbank ensure that for each deprecation listed in 19.0.0 release note, there is a blocking issue for 20.0.0 07 Jan 2020 Monitor Jira issues status:
the most forgotten 10 DM issues(resolution = Unresolved ORDER by updated asc) Support to J. Swinbank monitoring activity
DM-5713
-
Getting issue details...
STATUS
DM-6424
-
Getting issue details...
STATUS
DM-1781
-
Getting issue details...
STATUS
DM-6073
-
Getting issue details...
STATUS
DM-5609
-
Getting issue details...
STATUS
DM-6513
-
Getting issue details...
STATUS
DM-3406
-
Getting issue details...
STATUS
DM-3695
-
Getting issue details...
STATUS
DM-4949
-
Getting issue details...
STATUS
DM-5983
-
Getting issue details...
STATUS
3880 unresolved issues (3906 on November the 20th)
DM-5713 → Done. DM-6424 → Won't Fix. DM-1781 → Legit issue; low priority. Simply ignore for now? Or should we consider dropping loadLSST.csh
, since we clearly aren't prepared or able to maintain it? DM-6073 → Implementing an adopted RFC, but very low priority. Simply leave open for now. DM-5609 → Won't Fix. DM-6513 → Trivial; fix in progress (Fritz Mueller ) DM-3406 →Won't Fix. DM-3695 → Assigned as part of in-progress Qserv global spatial index work DM-4949 → Fritz Mueller . DM-5983 → Fritz Mueller . Add a point in the DMLT agenda in Monday morning telecon, in order that assignee people are aware.
Open Actions AOB Next DM-CCB December the 18th.
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions