Item | Description | CCB Notes |
---|
Flagged RFCs (To be approved by the DMCCB) | Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-593 |
---|
|
Planned end: Jun/14/2019 Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-581 |
---|
|
Planned end: Mar/15/2019 | |
Board Recommended RFCs | |
|
Adopted but not implemented LDM RFCs (only document RFCs) | |
|
Proposed RFCs (to review, do not require DMCCB approval) | Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-600 |
---|
|
Planned end: Jun/29/2019 Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-599 |
---|
|
Planned end: May/30/2019 Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-598 |
---|
|
Planned end: Jun/01/2019 Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-585 |
---|
|
Planned end: Jun/14/2019 |
- RFC-600 to be flagged:
- RFC-599: DMCCB agrees on the RFC but no action from to be taken
- RFC-598: should have been flagged
- if no comments, the RFC is approved
- RFC-585: no rush
|
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) | Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-596 |
---|
|
|
|
RFCs implemented since last CCB (to review, no action required) | Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-591 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | RFC-596 |
---|
|
|
|
Changes to the planned releases | - 18.0 Release status
- Community post out
- Planned first Release Candidate based on w_2019_22 (June the first)
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-19147 |
---|
|
|
|
Monitor Jira issues status: - the most forgotten 10 DM issues
- (resolution = Unresolved ORDER by updated asc)
| Support to J. Swinbank monitoring activity Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-4803 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-3036 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-887 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-1243 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-1757 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-4308 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-4439 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-1605 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-1606 |
---|
|
Jira |
---|
server | JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
---|
key | DM-1639 |
---|
|
4061 unresolved issues (4053 on May the 21st) | Pre-meeting notes from DMCCB#17 (2019 - 05 - 29): - With the exception of DM-4803, these are all Qserv issues. We should ask DMCCB#17 (2019 - 05 - 29) to address them.
- DM-4803 is broadly part of the same grouping as the persistence format questions we addressed last week (DM-4621, DM-4629). It's less unambiguously correct than those, though: we can clearly say that FITS files ought to be documented and/or self-documenting, but I struggle to get excited about whether they contain radians or degrees.
|
Open-Actions |
|
|
AOB |
|
|