Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

See section 7.4 for DMCCB organizational details.


2019 - 01 - 23 DMCCB #2

2019 - 01 - 15 DMCCB #1


Core members: 

Optional Members (involved when topics require their expertise):

  • Pipelines Scientist
  • Science Pipelines / Interface Scientist
  • T/CAMs


  • Determine when deliverables (controlled documents and software) are of sufficient maturity and quality to be baselined (placed under configuration controlled status) or released.
  • Review and approve/reject proposed changes to baselined items - any LCR must go through the DMCCB
  • Review and approve/reject proposed changes to the planned releases and their content
  • Review  all RFCs and and approves ’flagged ’ RFCs
  • Monitor DM Jira issues status (in support to the monitoring activity done by J.Swinbank )
  • Ensure that the DM Technical Baseline (LDM-xxx) documents  follow  LSST and DM configuration control processes
  • Monitor and approve  DM software releases


Every Wednesday 9.00 AM Pacific.

  • No labels