Page History

Current Sprint -  Sprint 28 (April 14, 2016 – April 27, 2016)

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

LexEVS Compatibility

• Remote service and client jar migration

LexEVS 6.4 Remote Service and Client Updates

caCore legacy code was mentioned and it was suggested that we should remove any caCore code.

Mayo will need to prioritize this work to determine where it will fit into our schedule. 

TODO:  Craig to create a JIRA item to track the removal of the caCore code.

PTE for CI and DEV environment discussion

• CI Server
• DEV Server

CI server - it was discussed that we may use an in-memory DB (HSQL) instead of MySQL DB.  This is being investigated by Mayo to see if we can get this working locally.

Scott noted that our Mayo Jenkins server is running on a system that has 8 cores with 32 GB of memory.

DEV server - Rob has installed LexEVS 6.4 runtime on DEV and generated the indexes.

There is a new 6.4 DEV container that Jacob is working on getting deployed.

NCI testing - NCI will build the 2.8 browser with the new LexEVS 6.4 jars and see if that runs without any code changes.

NCI will also test the runtime API and Tin will look at performance to compare 6.3 and 6.4.

Jason asked when the remote API will be available.  We suggested that it should be delivered by the end of sprint 29.  We will need to verify performance is still acceptable prior to releasing it to NCI.