Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ItemDescriptionCCB Notes

Flagged RFCs

(To be approved by the DMCCB)

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-575

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-579

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-581

  • RFC-575: DMCCB approve it and it is moved to "Board Recommend"
  • RFC-579: changes are highlighted in red
    • Changed to "Board Recommend"
  • RFC-581: to be decided next week

Proposed RFCs

(to review, do not require DMCCB approval)

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-578

  • No action to be taken from the DMCCB

Adopted RFCs without Triggering issues

(to create implementing DM issues)

None


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-571


RFCs adopted since last CCB

(to review, no action required)

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-576

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-577

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-573


RFCs implemented since last CCB

(to review, no action required)

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-555

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-559

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-558


Changes to the planned releases
  • New patch release based on 17.0 major release required:
    • Jira
      serverJIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyRFC-580
  • Question from John Swinbank : do we maintain 6 month schedule release or do we switch to releases based on functionality availability?
    • In practice: when will be science pipelines release 18?
  • 17.0 done
    • pipelines.lsst.io need to be updated with 17.0 information
    • Community post done today, linking to the 17.0.x branch documentation and updated when JSick will update pipelines.lsst.io
  • 17.0.1: approved, RFC set to "Board Recommend".
    •  Gabriele Comoretto to create the patch release 17.0.1 implementation issue, backport the change and work with Jonathan Sick to include this information in the release note.
  • Next release 18:
    • in 3 months time (June 2019)
    • WOM: would like to see releases based on features
    • Leanne: community also would like to see feature base release
    • Feature information is provided to T/CAMs from P6 and scientists; these are recorded in Jira as epics
    • What is missing is to relate these epics to a planned release

Monitor Jira issues status:

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

Support to J. Swinbank monitoring activity

  1. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2393
  2. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2790
  3. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2826
  4. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2824
  5. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2820
  6. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2589
  7. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2587
  8. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2563
  9. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2810
  10. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2819

3746 unresolved issues (3674 on Feb. the 20th)


All 10 issues have been reviewed during the CCB.

AOB
  • Should the DMCCB not be considering the RFC _after_ the triggered tickets have been created, rather than before?
  • AOB on RFC moved to next DM-CCB
  • LDM-635 draft in docushare need to be sent out for review
  • Semantic Versioning 2.0
    • Tim Jenness would like to apply it to each GitHub packages, it will simplify the dependencies management
      • This requires lot of work and has impacts on the build tools, continuous integration tools, releases, etc
    • Everybody agree that SemVer is the direction to move
  • An intermediate solution is to apply SemVer to to metapackages, that group together a smaller number of GithHub packages. This requires:
    • a proposal written down
      •  Gabriele Comoretto to draft a DMTN how to work with multiple metapackages depending one from the other
    • do some experimentation to see how it works
      • to do after conda env management has been clarified. See
        Jira
        serverJIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
        keyDM-16567

...