Page History

Sprint Status

Current Sprint -  Sprint 36 (August 04, 2016 – August 17, 2016)

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

Main work items that have been completed in sprint 3736:

• Tech stack - Java 8/CentOS7 testing and verification is complete.
• HTTPS updates have been completed and verified.

QA Tier Status

• Test update - Tin
• AppScan

Discussion Points:

• Testing is in progress.
• Tin requested an AppScan for CTS2 is requested.
• Will request AppScan for Remote API on Friday???

Decision Points:

Release Plan for

• • HTTPS
  • Tech Stack
  • Loaders

Discussion Points:

• If we give NCI one release with everything, they would have to test the browser and other clients (caDSR) with the upgrade to Java 8.
• Larry suggested this would be too much of a change for the clients at this time.
• Scott suggested delivering all of the code that is compiled in Java 1.7.
• Tracy mentioned that for the browser, they were able to redirect HTTP to HTTPS so end users were not forced to have to change their links.
• We discussed testing the current LexEVS 6.4 and whether to continue testing or wait until the HTTPS changes are added in.
  • Tin suggested halt testing until the new build is created.
• Larry suggested to create another build in Java 8. This would enable clients to test connecting to a Java 8 service and determine if their clients are compatible.

Decision Points:

• There will be no changes to 6.3.
  • This will run http.
  • It may be shutdown at the beginning of 2017.
• LexEVS 6.4.x 0 will be the HTTPS fix.
  • This will include the loader updates.
• LexEVS 6.5 will be the Tech Stack update.
• Mayo team will update the wiki page to show what changes are required to move to HTTPS.
• Mayo will rebuild LexEVS 6.4.0 to have the HTTPS and Loader changes. It will be re-tagged as the same 6.4.0.FINAL code base.
  • This will be built in Java 7.
• The CTS2 and LexEVS Remote API PTEs need to be updated to allow for HTTPS.
• Tickets need to be created to configure QA/STAGE/PROD for HTTPS.
• NCI needs to discuss with Systems to determine if they can handle parallel systems: one for HTTP and one for HTTPS.
  
  

Discussion Points:

• We asked if NCI had any comments on the backlog and priorities.
• Tracy suggested looking at the task to convert LexEVS to Maven.

Decision Points:

Discussion Points:

• No testing has been done.

Decision Points:

Discussion Points:

Decision Points:

LexEVS External Users

• Alexander
  

https://github.com/cts2/lexevs-service/issues/2#issuecomment-240205829

We assisted getting the user in configuring lexevs and cts2 and getting it up and running. This user will be loading HL7 next.

Mayo Team

• Deepak - Sept 1-6?, Sept 5
• Cory - August 12, Sept 5
• Scott - August 15, Sept 5
• Craig - August 24 -29, Sept 5

NCI

• Rob Wynne - Sept. 1-5