Page History

Current Sprint -  Sprint 27 (March 31, 2016 – April 13, 2016)

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint27

LexEVS Compatibility

• 6.4 vs. 7.0
• 6.3 and 6.4 indexes
• remote service and client jar migration

• API will remain the same.  
• However, changes to the jars (client) will be required.
• The requirement from NCI is that 6.3 users be able to use 6.4 content.
• Data Loaded would be loaded to 6.4
  • 6.4 indexes would be created
  • For 6.3 indexes would need to be rebuilt.
• NCI needs to plan on having both 6.4 and 6.3 indexes.
  • Additional storage will need to be obtained by NCI.
• Additional NCI 6.3 regression testing will need to be done to ensure 6.3 data is still correct.
• Analysis from Cory about migration to be discussed during the next week's meeting.
  • NCI will need to understand how extensive the changes are.
  • Based on the level of changes, thought needs to be given to releasing as 7.0 instead of 6.4.3
• It was suggested that 6.4 be released all the way to PROD to allow others to use/test. The URL would not be openly shared.

Value Set Issues

• Follow up/priorities

• Resolution still required:

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1731

  • Note: Not required for 6.4
• Needs Investigation:

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1729

  • Note: Not required for 6.4
• Work Arounds exist for:

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1730

  • Jira
    server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1732

Feature request to get qualifiers on properties (Metathesaurus)

• Discuss priority

• This impacts all coding schemes via CTS2 services.
• To be available for 6.3 and 6.4

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVSCTS2-35

• Last week there was dsicussion about configuring the CI environment with SQL. Scott noted that this might not be needed.
• This could be included as discussion for the ARC meeting.

• We will need to prepare ARC documents for 6.4
• We can copy our previous ARC document (as we don't have any changes).
• There may be an ARC meeting if deemed necessary.
• Provide by end of week to Jason.

• Tracy is going to evalute latest set of changes.