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-604
Planned end: Jun/20/2019

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-602
Planned end: Jun/20/2019

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-593
Planned end: Jun/15/2019

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-606
Planned end: Jun/30/2019

  • RFC-604 and 602 documents on the master branch
    • Kian-Tat Lim  says requirements should be good for now, but they may be improved in the future
      •  Leanne Guy and All DM-CCB to check that the documents in RFC-604 and RFC-602  
      •  Unknown User (gcomoretto) board recommend and issue the document once above action is done 
  • RFC-593, discussion postponed to next DM-CCB 
  • RFC-606: all CCB agree that this is fine, status changed to Board Recommend
Board Recommended RFCs

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-601
Planned end: Jun/07/2019

Adopted but not implemented LDM RFCs (only document RFCs)

None


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-605
Planned end: Jun/26/2019

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-600
Planned end: Jun/29/2019

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
keyRFC-585
Planned end: Jun/14/2019

  • RFC-605: John Swinbankthing thinks that the RFC needs to be better understood.
    • Wil O'Mullane flag this RFC and add a comment to address the discussion
  • RFC-600: Leanne Guy says that the RFC has been discussed and the LCR is ready to be pushed to project CCB
  • RFC-585: there is an action on Leanne Guy to discuss this with DESC in 2 weeks. End date to be moved forward

Adopted RFCs without Triggering issues

(to create implementing DM issues)

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


Adopted RFCs with all triggered work COMPLETED

(to set status as 'IMPLEMENTED')

None



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-603


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-213



Changes to the planned releases
  • 18.0 Release status
    • First Release Candidate based on w_2019_23 now available and under test
  • Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-19147
  • rc1 seems OK
  • Ready to prepare Characterization report
  • Release note to be done

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-5032
  2. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-5081
  3. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-5078
  4. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-5083
  5. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-5134
  6. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-3186
  7. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-3188
  8. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-3189
  9. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-1563
  10. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-861

3960 unresolved issues (4055 on June the 12th)

John Swinbank commentary:

  • DM-5032: won't fix.
  • DM-5081: valid; easy enough; not high priority.
  • DM-5078: wonder if we can eliminate PcaPsf; asked on the ticket.
    • Answer is yes; closed as “won't fix” and filed PIPE-31.
  • DM-5083: others (at least Unknown User (gcomoretto) &Kian-Tat Lim, I suspect) know better than I if this is relevant; KTL commented on the issue that this is low priority.
  • DM-5134 is done.
  • Others are all Qserv issues.
    • Unknown User (gcomoretto), would it be worth pinging the relevant T/CAMs before the CCB meets, so that Fritz Mueller  (in this case) has a chance to respond to these issues before we discuss them?

Fritz Mueller commentary:

  • DM-3188, DM-3189, DM-1563, and DM-861 are all to do with potential improvements to the Qserv integration test suites.  These are / may be valid and desirable improvements, but they are lower priority than finishing up features (e.g. ingest, multi-czar, and user-generated products support).  These are all already attached to epic DM-4828 ("Qserv Integration Test Improvements") which will be scheduled as time/priorities permit.
Open Actions

AOB

Next DM-CCB 

July the 3rd no DM-CCB

July the 10th, meeting to be run by Kian-Tat Lim

...