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, March the 20th.
Attendees
Regrets
DMCCB Meeting Goals See DMCCB responsibilities listed in LDM-294 section 7.4 Discussion Items Item Description CCB Notes Flagged RFCs
(To be approved by the DMCCB)
RFC-579Getting issue details...
STATUS
RFC-581Getting issue details...
STATUS
RFC-581: clarifications between MButler and KTL4 hour maintenance in the morning, in case this is required. It may be shorter, It may not be needed. TJ: Are problems during daily maintenance counted as time lost? KTL: This should be time reserved for maintenance, without causing any data lost MB: the terminology need to be clarified. RFC:579 is adopted already Proposed RFCs
(to review, do not require DMCCB approval)
RFC-582Getting issue details...
STATUS
RFC-583Getting issue details...
STATUS
RFC-582 is adopted RFC-583 discussion ongoing, no action for this week. Upgrading the scipipe_conda_env may solve the problem. 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-580Getting issue details...
STATUS
RFC-575Getting issue details...
STATUS
RFC-578Getting issue details...
STATUS
RFCs implemented since last CCB
(to review, no action required)
RFC-574Getting issue details...
STATUS
RFC-572Getting issue details...
STATUS
RFC-571Getting issue details...
STATUS
RFC-576Getting issue details...
STATUS
Changes to the planned releases 17.0.1 patch release work in progress
DM-18331Getting issue details...
STATUS
Validation completed, just missing the final tag. Monitor Jira issues status:
the most forgotten 10 DM issues(resolution = Unresolved ORDER by updated asc) Support to J. Swinbank monitoring activity
DM-2970Getting issue details...
STATUS
DM-2969Getting issue details...
STATUS
DM-2968Getting issue details...
STATUS
DM-2687Getting issue details...
STATUS
DM-1660Getting issue details...
STATUS
DM-2422Getting issue details...
STATUS
DM-803Getting issue details...
STATUS
DM-2476Getting issue details...
STATUS
DM-2850Getting issue details...
STATUS
DM-1867Getting issue details...
STATUS
3819 unresolved issues (3746 on March. the 6th)
No comments from the participants: AOB Should the DMCCB not be considering the RFC _after_ the triggered tickets have been created, rather than before? New conda environment
DM-17684Getting issue details...
STATUS
RFC process discussion requires John Swinbank to come back New Conda Environment: need to wait for John Swinbank to be back to rebuild the shared stack and Joshua Hoblitt to ensure that the update to the Jenkins scripts are OKCommunity Post required, plus 3 PRs TJ: Do we need to RFC this conda env change? YesWe are proposing a change to the baseline to Python 3.7 and numpy 1.16. EUPS stub packages must be modified to reflect the new baseline. Unknown User (gcomoretto) file an RFC on conda Environment: declare versions changes, python, astropy, numpy, matplotlib and scipy 20 Mar 2019 Unknown User (gcomoretto) Run rebuild with the new environment for lsst_distrib, lsst_ci and ci_hsc 20 Mar 2019
Pending Flagged RFCs
Pending Proposed RFCs
Oldest issues
Meeting outcome
Pending DMCCB Actions
1 Comment
Wil O'Mullane
I may not make the CCB - Already approved RFC-579. As long as NCSA say ok no problem with RFC-581