Page History

Sprint Status

Current Sprint -  Sprint 32 (June 9, 2016 – June 22, 2016)

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

• We completed the code clean up task
• We pushed out the 6.4 artifacts from the previous sprint.  
• 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:

Gilberto suggested that LEXEVS-1153 should be fixed by fixing the other OWL2 loader issues.  

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. The Mayo development team verified that the property qualifiers are showing up.

Tracy has contacted CTRP about this update.

NCI DEV deployment updates

• All Services

6.4 CTS2 hasn't been deployed to DEV yet.

Tracy will wait for the artifacts from sprint 31 and then deploy 6.4 CTS2.

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 separate issue for the "Map to" part of this issue. 
• This is a high priority issue that should be done for 6.4.

• (Tracy/Rob)

Unexpected behavior found in searching value set using LexEVSValueSetDefinitionServices API

End-to-end CI testing environment updates (Cory/Scott)

Larry suggested the following approach for what will be on PROD:

• LexEVS 6.4 will go to PROD and be available.
• There will a single database with 2 indexes (one for 6.3 and one for 6.4)
• 6.3 will still be the default LexEVS API
• CTS2 REST will default to 6.4
• The browser will use 6.4 LexEVS API
• The community 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:

• CTS2 REST services will be available
• Clients will need to rebuild jars if they move to 6.4.
  • We will need to provide a migration path

LexEVS External Users

• Updates