Page History

• RFC-593: end date moved to July 31
• RFC-605: seems fine, but RLupton would like this to be fixed somewhere else
  • Technote could be written but no time for it
  • To keep on hold: to move the end date one week
• RFC-617: for the CCB point of view it is fine. Add a comment.
• RFC-611: 
  • section 3 to be renamed Verification Control
  • Ready to be adopted
• RFC-612:
  •  Unknown User (mbutler) to read LDM-552
  •  Unknown User (gcomoretto) to add a draft in DocuShare (as per process)for LDM-552 
• RFC-613: LDM-152
  • so far no problems from the DMCCB, the 
• RFC-614: LDM-148
  • new product tree and some minor changes
  • OK
• RFC-615: LDM-144
  • Kian-Tat Lim has a look and changes seems reasonable, some concerns about costs increasing
  • Unknown User (mbutler) the model used to do this estimation is quite old, and it should be reviewed
  • Kian-Tat Lim suggests not to modify the baseline, but to submit the document to the review as a draft.
  • DM-CCB decided not to Board Recommend the RFC and review the document trying to reduce the costs.
• RFC-619: LDM-672
  •  Unknown User (gcomoretto) to add a draft in DocuShare of LDM-672

None

• 18.0.0 Release status
  
  • Release completed.

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

• Next Releases:
  • proposed 18.1.0 as per RFC-618

• RFC-618: DMCCB is fine
  •  Unknown User (gcomoretto)to open a release issue Jira issue for the 18.1.0 release and comment on the RFC-618, release to be completed available in 2 weeks

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

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

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

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

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

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

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

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

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

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

3957 unresolved issues (3937 on July the 10th)

•  Unknown User (gcomoretto)to open a Jira issue to update the DevGuida with John's proposed deprecation procedure in DM-20119