Page History

Sprint Status

Current Sprint -  Sprint 37 (August 18, 2016 – August 31, 2016)

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

The Mayo team is working on testing features and mavenizing the remote client.

QA Tier Status

• AppScan

Discussion Points:

• The remote API appscan had an issue that was fixed by the systems configuration team.
• The CTS2 appscan didn't really test the REST services. The scan tried to find the WSDL, but that didn't do anything.
  • The appscan would need to know how to construct our REST calls.
  • Larry suggested that the tests didn't find any issues and that should be suffice.

Decision Points:

• We decided the appscan is fine and we can move on.

Release Plan for 6.4.1

• • PTEs updated

Discussion Points:

• The lexevs 6.4.1 artifacts are on the SFTP site now.
  • Links to the artifacts can be found here: LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint37
• LexEVS Software Release Identifiers - This wiki page gives an overview of the sub components/artifacts and what fixes are included.

Decision Points:

• The NCI team will deploy to DEV and test.

OWL2 Loader Verification

• Jira
  server NCI Tracker serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2245

Discussion Points:

• There is concern about the OWL2 loader issue of the Thesaurus.
• Scott asked if we need to fix this now.
• Tracy mentioned that we are not loading OWL2 into production.
• In the future we should be test loading the thesaurus with OWL2

Decision Points:

• We will push hold off on the OWL2 off fix until next sprint before considering it.

HTTPS document review

Discussion Points:

• Remote Client HTTPS Requirements
• We went over the changes for the remote client as well as for the CTS2 REST client.
• In order to help clients understand if clients need to make changes, Larry suggested that we add some text to have the end user contact us with their sample code.

Decision Points:

• Scott will add a message to the https document that the end users can send the Mayo team a snippet of their code and we can assist in analyzing what changes (if any) they would need to make.

LexEVS External Users

• Alexander
  

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

We have responded to the user that the fix has been checked in for the issue he found.

Mayo Team

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

NCI

• Rob Wynne - Sept. 1-5