Page History

...

Action Items

...

Agenda

...

Sprint Status	Current Sprint -  Sprint 41 (October 13, 2016 – October 26, 2016) 16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint41 Completed Lexevs 6.4.1.1 artifacts Completed some Java 1.8 tasks Assisted with issues found during the sprint.
6.4.1 Deployment/Testing status	Discussion Points: This is in Production now.  CaDSR is using this version Decision Points:
6.4.1.1 Build and Deployment Testing on QA Valueset resolution issue on STAGE	Discussion Points: This issue can be fixed in the data, but a code fix is preferred. This issue is also observed in 6.3 PROD. The NCI dev team has a script that can detect if a valueset is empty. Mayo team will investigate how empty value sets behave and what happens when a null version is encountered. Decision Points: Larry suggested that 6.4.1.1 will continue to be tested and move up the tiers. Larry suggested that value set patch could be included with the Java 1.8 release (LexEVS 6.4.2). There is a workaround for the value set patch.	6.4.1.1 Build and Deployment Testing on QA	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 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 Jira server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-2414 LEXEVS-2413 - Kim mentioned that the browser is passing in a hash set in its code, but is not seeing this error. We will investigate LEXEVS-2412  (OBI) to determine if this is a loader or code issues. If this is a code issue, we will need to determine what release they would go in. 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.
Valueset resolution issue on STAGE	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
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	Discussion Points:  Discussion Points: Decision Points:
NCI Nexus Server Migration Update	Discussion Points: Mayo team will meet had a meeting on Monday with Sarah and the SCM team to discus long term team.  They will look at automating the maven script for publishing artifacts first, then look at the ANT Decision Points:
CTS2 URLs for 6.3 and 6.4	Discussion Points: Are users pointing to non HTTPs URL?CTRP verification of HTTPS URL. Decision Points: CTRP is using the CTS2 6.3The contact person is Emont.  We should have them validate 6.4.1 HTTPs URL and perform some search testing on PROD. If they don't find any issues, we should be able to make 6.4.1 HTTPs URL the default. Larry will contact CTRPTracy will contact this person to see if they have tested the HTTPS URL.
MySQL database upgrade for LEXEVS	Discussion Points: An NCI DBA team is in the process of migrating MySQL from 5.5.38 to 5.6.33. LexEVS breaks with MySQL 5.6.  This will require Decision Points: Jacob is working with the DBA team to determine when 5.6 is required. 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:
DEV deployment process	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 work. 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 F2F Planning PIV card process	Discussion Points: Face-to-Face Wiki: LexEVS 16X237 2016.12 Technical Face-To-Face Meetings Decision Points: Mayo will create a wiki page for the F2F planning to capture our suggestions.  Put a pointer to the previous F2F on the new wiki. Propose F2F Agenda Topics Proposed F2F Agenda Topics Sherri will need to leave on Friday by 2:00 PM. Decision Points:
LexEVS External Users	https://github.com/cts2/lexevs-service/issues/15 Multiple targets in mappings source not working?	LexEVS External Users	There was a user that was running CTS2 without connected to the internet.  Schema files currently require an internet connection to obtain.
Team Absences	Mayo Team Cory - October 20,21 Scott - October 21 Craig - NCI Larry October 20 - November 7 Tracy Nov 8 Dec 14-16 Jan 9-17 Feb 21-24 Rob 10/21 – AM only 11/2 11/14 – PM only 11/24-11/28 12/9 12/19 12/23-12/27 1/2/2017

...