Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Sprint Status

Current Sprint -  Sprint 31 (May 26, 2016 – June 08, 2016)

LexEVS 6.4 Agile Development - Sprint Status

We have completed sprint 31. The following tasks were completed:

• We completed some code clean up and pushed out the 6.4 artifacts.  
• We also worked on remote api tests to make more generic. This will need to be expanded to provide more test coverage in the next sprint.
• LEXEVS-1729 was fixed as well.

For sprint 32, we will start work on the following issues:

• We will be delivering the 6.4 artifacts from sprint 31 in the next couple of days.
• Work on the OWL 2 loader issues
• Provide additional test coverage for the remote API.
• Based on today's suggestion, Gilberto suggested the HL7 loader issue should be put at the bottom of the list , after the OWL2 loader issues - LEXEVS-1037.
• LEXEVS-1153 should be fixed by fixing the other OWL2 loader issues.  
  • We will drop the priority to the last OWL2 loader issue to look at.

We are also managing the final deliverables for the 6.4 projects.

6.3 CTS2 service deployment

• Update from Tin

This has been deployed to PROD. We verified that the property qualifiers are showing up.

Tracy has contacted CTRP about the udpate. 

NCI DEV deployment updates

• All Services

6.4 CTS2 hasn't been deployed.

Tracy will wait for the artifacts from sprint 31 to deploy them.

Deployment Approach

• RC1 Delivery
  

LexEVS 6.4 Git Tags and Artifact Naming Conventions

After discussing with NCI, we decided that we will create an RC build on DEV.

When tested/ready, we will create a FINAL tag for QA.

• This build/tag will not change any further up the tiers. This will satisfy NCI's requirements.

Cory will update the document to reflect these changes.

OWL2 Approach (Prioritized)

 We discussed this above.

Hyphenated Word - Contains Search

• Verification (Kim)

Complex Properties Hardcoded

Tracy indicated that in OWL2, there should be no hard coding.

We should derive from the context. If it can't be then it should be taken from the preferences.

For priority, Gilberto suggested that this should be fixed as part of the OWL2 loader issues.

Rob suggested that other teams would like to use the "Map to" feature.

• Tracy will create a seperate issue for the "Map to" part of this issue. This is a high prioritiy issue

Larry suggested the following:

• 6.4 will go to PROD.
• A single db with 2 indexes
• 6.3 will still be the default LexEVS API
• CTS2 REST will default to 6.4
• Browser would use 6.4 LexEVS API
• The communitiy will be made aware of 6.4 and they can test

We should document 6.4 on the wiki. Make sure to include the following points:

• REST would be available
• Clients will need to rebuild jars if they move to 6.4.
  • Provide a migration path

Looking forward to 6.5, we will need to look into replacing MySQL with MariaDB for better graph performance.

LexEVS External Users

• Updates