NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 1

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version 2

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sprint Status

 

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

LexEVS 6.4 Agile Development - Sprint Status

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

Testing on Dev and QA

  • QA Verification Process

 

Discussion Points:

  • The lexevs 6.4.1 artifacts are on the SFTP site now.
    • 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 VerificationDiscussion

    • Jira
      serverNCI Tracker
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-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 hold off on the OWL2 fix until next sprint before considering it.

    HTTPS document review

    • End user communication update

    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:

    Decision Points:

    NCI Jenkins Plan/Configuration

    Discussion Points:

    Decision Points:

    CTS2 over RMI

    • Future Need

    Discussion Points:

    Decision Points:

    NCI Nexus Server

    • Mayo to migrate to NCI's server
    		 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. 

    Team Absences

    Mayo Team

    Deepak - Sept

    1

    2-

    6?, Sept

    5

    • Cory - Sept 5, Sept 8-9
    • Scott -Sept 5
    • Craig - August 24 -29, Sept Sept 5

    NCI

    • Rob Wynne - Sept. 1-5

    JIRA Issues

    ...