Skip to end of metadata
Go to start of metadata

Location

BrowserRoom SystemPhone Dial-in
https://bluejeans.com/761546516/
  1. Dial: 199.48.152.152 or bjn.vc
  2. 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

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

RFC-579 - Getting issue details... STATUS

RFC-581 - Getting issue details... STATUS

  • RFC-581: clarifications between MButler and KTL
    • 4 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-582 - Getting issue details... STATUS

RFC-583 - Getting 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)

None


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

None


RFCs adopted since last CCB

(to review, no action required)

RFC-580 - Getting issue details... STATUS

RFC-575 - Getting issue details... STATUS

RFC-578 - Getting issue details... STATUS


RFCs implemented since last CCB

(to review, no action required)

RFC-574 - Getting issue details... STATUS

RFC-572 - Getting issue details... STATUS

RFC-571 - Getting issue details... STATUS

RFC-576 - Getting issue details... STATUS


Changes to the planned releases
  • 17.0.1 patch release work in progress
    • DM-18331 - Getting issue details... STATUS
    • Validation completed, just missing the final tag.
  • Gabriele Comoretto update / Replay on the 17.0 community post. Complete the release note.  

Monitor Jira issues status:

  • the most forgotten 10 DM issues
    • (resolution = Unresolved ORDER by updated asc)

Support to J. Swinbank monitoring activity

  1. DM-2970 - Getting issue details... STATUS
  2. DM-2969 - Getting issue details... STATUS
  3. DM-2968 - Getting issue details... STATUS
  4. DM-2687 - Getting issue details... STATUS
  5. DM-1660 - Getting issue details... STATUS
  6. DM-2422 - Getting issue details... STATUS
  7. DM-803 - Getting issue details... STATUS
  8. DM-2476 - Getting issue details... STATUS
  9. DM-2850 - Getting issue details... STATUS
  10. DM-1867 - Getting issue details... STATUS

3819 unresolved issues (3746 on March. the 6th)


  • No comments from the participants:
    • No actions this week.
AOB
  • Should the DMCCB not be considering the RFC _after_ the triggered tickets have been created, rather than before?
  • New conda environment
  • 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 OK
    • Community Post required, plus 3 PRs
    • TJ: Do we need to RFC this conda env change? Yes
      • We 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.
      • Gabriele Comoretto file an RFC on conda Environment: declare versions changes, python, astropy, numpy, matplotlib and scipy  
      • Gabriele Comoretto Run rebuild with the new environment for lsst_distrib, lsst_ci and ci_hsc  


Pending Flagged RFCs

Key Summary
Loading...
Refresh

Pending Proposed RFCs

Key Summary
Loading...
Refresh

Oldest issues

Key Summary
Loading...
Refresh

Meeting outcome


Pending DMCCB Actions

DescriptionDue dateAssigneeTask appears on
  • Leanne Guyto talk to desc about  RFC-585 - Getting issue details... STATUS   if this has some impacts on them   
19 Jul 2019Leanne GuyDMCCB#12 (2019 - 04 - 24)
Michelle ButlerDMCCB#21 (2019 - 07 - 17)
John SwinbankDMCCB#20 (2019 - 07 - 10)
  • Tim Jenness to clarify in the Developer Guide that the DM-CCB can ask triggered issues can be opened on an RFC before approving it.
Tim JennessDMCCB#9 (2019 - 03 - 27)
  • Tim Jenness to update dev guide with the proposed procedure for merging an approved RFC ticket.
Tim JennessDMCCB#4 (2019 - 02 - 06)

1 Comment

  1. I may not make the CCB - Already approved RFC-579. As long as NCSA say ok no problem with RFC-581