Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Sprint Status

Current Sprint -  Sprint 42 (October 27, 2016 – November 9, 2016)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint42

• We discovered an issue that was fixed (LEXEVS-2413) in lexevs release 6.4.1

• .2.
• We are looking at the issues that the NCI team is running into (mentioned below).

Discussion Points:

• This is in Production now.  CaDSR is using this version

Decision Points:

6.4.1.1 2 Build and Deployment

• Testing on QAStatus

Discussion Points:

• There are some issues found in this release
  

  Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-

  2412

  2413

• Build will be finalized today and NCI team will deploy the QA.

Decision Points:

Duplicate resolved valueset issue on STAGE

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-

  2413

  2415

Discussion Points:

• Tracy believes the code is running as designed.
• The issue might be on the resolved valueset and what is being returned.
• Scott is still investigating and attempting to recreate the issue at NCI.

Decision Points:

• Scott will continue to look into this and work with Tracy and Kim.

Decision Points:

• LEXEVS-2413 - Scott will verify if this is a java 1.7/18 issue or if it is just an API level issue.

Discussion Points:

• This seems to work fine with the OWL2 loader.

Decision Points:

• Tracy agrees that we can use the OWL2 loader as a solution to this problem.
• We will need to verify that the OWL2 loader will load all the correct objects as the previous OWL loader.
• Scott will update the JIRA issue with these updates.

Discussion Points:

• This issue was resolve by fixing the data load.
• Tracy suggested that we add a loader preference to set the value set version.

Decision Points:

• Scott will investigate this issue and see if anything breaks and then propose a solution, if needed.This test plan and execution will be added to the JIRA item

Discussion Points:

• On DEV the load was correct.
• On DEV the API was failing to query properly.

Decision Points:

• caDSR will need to verify this works for them.  (Tracy did let them know it is there to test)
• Scott will update the JIRA issue with these updates.

Loader Issue and logging

• Tracy to discuss

Discussion Points:

• Logging for loaders is not adequate.
• NullPointerExceptions are bubbled up.
• The manifest load is currently exhibiting this issue.
  

Decision Points:

• The development team will need to enhance the logging.
  • Inspect exceptions and determine if there is any additional messages that need to be logged.
• Scott to create a new JIRA issue to track this.
  • We will need to prioritize this and discuss with Larry and team.
    

NCI Nexus Server Migration Update

Discussion Points:

• Mayo team had a meeting on Monday We are planning on meeting with Sarah and teamtomorrow. 
• They will look at automating the maven script for publishing artifacts first, then look at the ANT
  

Decision Points:

Discussion Points:

Decision Points:

• The contact person is Emont. 
• Tracy will contact this person to see if they have tested the HTTPS URL.

MySQL database upgrade for LEXEVS

Discussion Points:

• An NCI email states- "All MySQL Development databases except LEXEVS databases, related applications, and related servers could be restarted during this patching window."  
• Jacob is working with the DBA team to determine when 5.6 is required. 

Decision Points:

• Tracy will work with CTRP for verification of HTTPS URL.

Discussion Points:

• The Mayo team would like to have a dev server that we would push out the latest snapshot code to at the end of the sprint.
• The Mayo team would maintain the lexevs software on this system.
• Tracy mentioned that the only one that would use the lexevs release would be the browser.
• The dev server could be a VM.
• We could also use the existing DEV server for this workJacob will create a DEV VM for the Mayo dev team to deploy to and test.

Decision Points:

• We will work with Jacob to determine if we need a new dev instance or if we can use the existing DEV server

F2F Planning

Discussion Points:

• Face-to-Face Wiki:
  • LexEVS 16X237 2016.12 Technical Face-To-Face Meetings
• Propose F2F Agenda Topics
  
  • Proposed F2F Agenda Topics
• Sherry added a prioritization session.
• The Mayo team will be on site the whole week to allow time for the PIV card processSherri will need to leave on Friday by 2:00 PM.
  

Decision Points:

• Add agenda item: CTS2 and FHIR project that Harold is involved with.

https://github.com/cts2/lexevs-service/issues/15

Mayo Team

• Cory -
• Scott -
• Craig -

NCI

• Larry
  • October 20 - November 7
    
• Tracy
  • Nov 8
  • Dec 14-16
  • Jan 9-17
  • Feb 21-24
• Rob
  

  • 11/2

  • 11/14 – PM only

  • 11/24-11/28

  • 12/9

  • 12/19

  • 12/23-12/27

  • 1/2/2017