Page History
...
Sprint Status | Review Sprint 3 (finished)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sprint 4 Planning / Roadmap impact | Sprint 4 Overview
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sprint Planning | Issue Grooming
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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) CDRP 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ARC Meeting Update | 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Design and Architecture Review Meeting Planning | Schedule for Thursday or Friday Larry will set up a meeting for Friday. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Next Release Planning - 6.4 or 7.0? | The question arose because Lucene is a large feature change, but the LexEVS API will not change. The suggestion is to go with 6.4 so external users wouldn't be concerned about large changes. If we don't implement all of the search algorithms, then that could be an API change.
The suggestion is to go with 6.4 so external users wouldn't be concerned about large changes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
JIRA item - Sorting for Tree Hierarchy | Extraneous roots issue - we haven't been able to replicate here. Request Scott thought there was an additional request to sort the results.This may not be an issue as Kim confirmed this was not the case and there was nothing more to be done. As long as we don't make any changesbreak the current behavior, there is no concern. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
JIRA item - RRF Loader resolution | 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 we can work on when time permitsit will be placed in the backlog until it is prioritized for a future release. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Tree Extension Code Merge to LexEVS repository discussion | 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 summary 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 | Gilberto will be back next week to discuss. |
...