LexEVS Meeting Minutes - 2015.1.21

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

on hold

on hold

on hold

done

open

Scott: 

• Backwards compatibility issue LEXEVS-689
  • Tree related. Kim and Scott identified a code path that hasn't been previously discovered.
• OWL Updates
  • Discussion below.
  • Gilberto and Scott had a duplicate discussion - more details below.
• Lucene planning
  • Continued planning, trying to develop a roadmap and way of managing the project.

Cory:

• JIRA Agile Configuration.
  • 6.4 planning - adding agile related activities.
• Waiting for AppScan Results for nodeJS
  • Waiting for results.
  • Tracy thought the results came through.
• Lucene planning

Kevin:

• Lucene Planning
• GitHub release and development planning
• JIRA-636
  
  

Craig: Project Plan for 6.3 and 6.4

• Lucene planning.
• 6.3 release.
• Agile Configuration
  
  

Confirm tagging and deploying to Dev

• 2 development tasks remain to be completed and are expected to be complete by Jan 28.  
• As discussed last week, 6.3 will not be an official release.  
• 6.3 will be deployed on NCI Dev for continued 2.7 browser development.
• All fixes in 6.3 will be officially deployed to Production in the 6.4 release.  
• no timeline established for 2.7 browser. Once plan in place, then we can decide on deploying 6.3.
• Craig to update plan and remove deployment tasks.

Deployment of Node.JS (so we can point to 6.2 services)

• Can we have it available for 6.2 announcement? Getting it pushed up to Production will require quite a bit of time.
• In the short-term, Cory will deploy on informatics and point to the 6.2 Production service.

Nothing

Questions about DNS naming conventions.

• If there are changes, Mayo will need to know so we can update the release artifacts.
• lexevsapi6 url was added (generic)
  • This is to remain valid across 6.2, 6.3, 6.4, etc

Discussed the list of fixes (captured in spreadsheet) and those will be added to JIRA.

Gilberto and Larry discussed and there are additional things to be considered in the near term.

Would like to cover all the main features in the 6.3 timeframe. In the spreadsheet, the 5 (high priority) will be done first and continue down until 1. Scott and Gilberto will need to have further discussions. This effort will push out schedules (6.4).

Kim identified "Sorting the mapping table" as a problem. Mayo team to review.

NCI team would point the term browser to the remote API to see if anything is broke.

It was discussed that we should not depend on anthill pro. Scott suggests that automation be for individual services (not one for all). There are some projects at NCI that uses Jenkins.

In house deployment - lengthy process, often doesn't go quite right. If we could automate, then more frequent updates to make things available. Warren has been pushing this moving forward.

Mayo team to discuss - when would it make sense to tackle this and start planning.