Sprint Status | Current Sprint - Sprint 49 (February 2, 2017 – February 15, 2017) 16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint49 |
DEV blade Server | Discussion Points: - Larry mentioned that Jacob said the DEV blade server is ready.
Decision Points: |
LexEVS Java 1.8 & MySQL 5.6 Environment | Discussion Points: - MySQL 5.6 is loaded and ready for use/testing.
Decision Points: |
Road map to 6.4.2 release | Discussion Points: - Migrating to LexEVS 6.5.0
- Cory is merging all 6.4.1.3 changes into the 6.4.2 branch of code.
- Larry suggested adding workflows to the migration wiki for migrating the Java API, and REST
- How does the user know what LexEVS components and versions they are using?
- We need to provide the user with places to look in their software in order to determine what LexEVS components they are using.
- Example: If you are using <base URL>/"GetXML" method, then you are using the Data Service that will be going away.
- We could structure this as a FAQ.
- How do I know it affects me?
- How does it affect me?
- How do I update?
- The Apache logs may indicate what services are being used (or at least the URLs).
Decision Points: - Scott to update the document.
|
Next LexEVS Release Version | Discussion Points: - Dropping the legacy Data Services is an API change.
- The other existing APIs have not changed.
Decision Points: - Mayo team to determine what new jars were added for the upgrade to Java 8. Add this to the NCI wiki.
- Clients may need to update these jars.
- Larry suggested that we add a section to the migration wiki for Java 8 migration issues that end users will encounter.
- Include issues that the Mayo team ran into as well as other migration links from Oracle, if applicable.
- LexEVS 6.4.1.3 will be running in parallel with LexEVS 6.4.2 while clients migrate.
- Based on our discussions we agreed the version will be 6.4.2.
|
6.4.1.3 Snapshot build update | Discussion Points: - LexEVS 6.4.1.3 Release Notes
- Rob was able to verify LEXEVS-812.
- Rob wasn't sure how to verify LEXEVS-2585.
- Scott suggested there was an example in the JIRA issue.
Decision Points: |
Value set loads with OWL2 source for NCIT | Discussion Points: - Scott suggested there is not enough support in OWL2 to resolve value sets.
- Scott will work with OWL2 loads to investigate further.
- Scott asked when OWL2 will be used in Production (for prioritizing our work).
- Gilberto mentioned that they will be migrating at the end of March, 2017.
- The first version of the NCIT in OWL2 will come out the end of April.
Decision Points: - Based on the discussion, Scott will continue his work on these issues in the current sprint.
- Larry suggested that there should be an announcement that NCIT is transitioning to OWL2.
|
MAX_CHILDREN in the TreeService getTree method | Discussion Points: - This is a a tree extension issue. The JSON is not sorted.
- Kim has a workaround for this.
- Kim requested that the tree extension issues should be worked on. This will help to make the browser more reliable.
Decision Points: |
URI Resolver over HTTPS | Discussion Points: - All tiers have been updated to use the URI Resolver over https.
Decision Points: |
eCache issue update | Discussion Points: - Jacob sent the links to all of the logs on Prod. This will allow the dev team to review the logs when a user runs into this issue again.
Decision Points: |
LexEVS External Users
| Discussion Points: - Craig introduced Mary to the correct contacts for her value set usage.
Decision Points: |
Proposed Backlog Review Items | Discussion Points: Decision Points: - Craig will create a list of issues to prioritize and send out a list.
|
Team Absences | Mayo Team NCI |