Page History

• RFC-593: dome discussion ongoing
  • Kian-Tat Lim  is OK to accept it (from a slack message)
• RFC-620: it requires to be escalated to the project CCB
  • John Swinbank says that Mario would like to have this approved, so it can announce the outcome to the wider community
    • there will be continuous iteration between Mario and science team, can the DMCCB recommend it and the let the iteration move forward?
  • Tim Jenness :
    • LDM-151 is inside DM,
    • LSE-163 (and LSE-61) requires project CCB approval, that imply Jellico approval, that should not be a problem
    • It is fine to board recommend the RFC if Colin and Leanne are fine with it.
  • Colin Slater requested some changes, but still, nothing has been done. There are some details missing.
  • DMCCB may need to board recommend this via slack, once Leanne gives the OK.
• RFC-623:
  • John Swinbank is Ok with it, but he is worried that people may waste story points on old code to made snake_case
    • the RFC can be adopted with an explicit statement
    • every few months people will be asking to convert camel case to snake case
  • Tim Jenness is also OK with it but has the same worry
  • Leanne Guy suggests giving snake case approval only for dafbutler package.
    • Jim shall file a new RFC, and DMCCB discuss a bit longer on RFC-623
    • No further discussion on RFC-623 are required, is recommended (now) or not.
  • DMCCB agreed on the RFC, ONLY new code only to be snake_case.
    •  John Swinbank to comment with the DMCCB discussion outcome and recommend RFC-623 29 Aug 2019 

Unknown User (gcomoretto) comment added to the RFC, asking to approve it.

None

None

• Next Releases:
  • 18.1.0 completed
• Next Major release 19.0.0
  • Autumn 2019

Support to J. Swinbank monitoring activity

1. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-2640

2. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-2908

3. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-3590

4. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-1574

5. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-1016

6. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-1103

7. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-1106

8. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-1105

9. Jira
   server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-1104

10. Jira
    server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 key DM-3349

4000 unresolved issues (4031 on July the 31st)

John Swinbank says:

• DM-2640 → Seems valid. Added comment.
• DM-2908 → Seems valid. Added comment.
• DM-3590 → Won't Fix.
• DM-1574 → Is a SQuaRE ticket, but it seems unlikely that they would address it. My suggestion is to “Won't Fix” it; I've asked the reporter for their opinion.
• DM-1016 → Reassigned to DM Science; not a high priority.
• DM-1103, DM-1104, DM-1105, DM-1106 → Won't Fix (obsolete).
• DM-3349 → Now in review reviewed done.