Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Review Sprint 3 (finished)

• Goal: 
  
  • Take what we learned from Sprint 2 and revise the roadmap to better reflect the development plan.   
  • Obtain NCI signoff on project documentation (as per SOW)
  • Prepare the development environment (GIT and Fisheye)
  • Provide continued support and issue resolution.
• Project Roadmap
  • https://wiki.nci.nih.gov/download/attachments/270532635/S13-500%20MOD4%20-LexEVS%20Lucene%20-%20Project%20Roadmap%20-%2020150415%2020150420.pdf?api=v2

• Agile Board
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220
• Report 
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220&view=reporting&chart=sprintRetrospective&sprint=287
• Retrospective 
  • 2015-04-21 Retrospective - 6.4 - Phase - Architect & Design - Sprint 3
• Deliverables 

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

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

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

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

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

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

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

Sprint 4 Overview

• Goal:  
  
  • Obtain NCI signoff on project documentation (as per SOW)
  • Prepare the development environment for 6.3 RC2
  • Resolve 6.3 JIRA issues prioritized for 6.3 deployment.
  • Provide continued support and issue resolution.
• Project Roadmap
  • https://wiki.nci.nih.gov/download/attachments/270532635/S13-500%20MOD4%20-LexEVS%20Lucene%20-%20Project%20Roadmap%20-%2020150420.pdf?api=v2
• Agile Board
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220
• Report
  • https://tracker.nci.nih.gov/secure/RapidBoard.jspa?rapidView=220&view=reporting&chart=sprintRetrospective&sprint=301

Issue Grooming

• Prioritize JIRA issues

LexEVS 6.3 logistics

Will LexEVS 6.2 persist once 6.3 is deployed?

Goal is to move to the most recent service (6.3).

CaDSR is testing LexEVS 6.2 (not complete)

CTPR will need to test yet.

Tracy mentioned that there are not many users on LexEVS 6.2 yet.

The TERMS browser will need to test on 6.3 to make sure it works as expected.

The plan then is to reuse the 6.2 containers and URLs for LexEVS 6.3.

LexEVS 6.3 and the CTS2 API documentation service ARC meeting went well.

We need to create a PTE for the CTS2 API documentation service.

Schedule for Thursday or Friday

Larry will set up a meeting for Friday.

The question arose because Lucene is a large feature change, but the LexEVS API will not change.

If we don't implement all of the search algorithms, then that could be an API change.

• "Result Ranking" should be good, but the exact same rank from the previous LexEVS release is not required.

The suggestion is to go with 6.4 so external users wouldn't be concerned about large changes.

Extraneous roots issue - we haven't been able to replicate here.

Scott thought there was an additional request to sort the results.  Kim confirmed this was not the case and there was nothing more to be done.  As long as we don't break the current behavior, there is no concern.

A new JIRA item was created to capture the need to clean up the RRF loader (as per LEXEVS-879).

This issue was discussed and it will be placed in the backlog until it is prioritized for a future release.

This would tie the tree extension to a specific version of LexEVS.  The tree extension usually needs to stay in sync with LexEVS change anyway.

The overall conclusion is to pull the tree extension into the LexEVS code base within Git.

TODO: Create a JIRA item and add this to the 6.3 release.

JIRA Plugin - Update from Gilberto