Page History
...
Sprint Status | Current Sprint - Sprint 27 (March 31, 2016 – April 13, 2016) LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint27 We discussed Sprint 28 work that is planned. Larry was asking when we can deliver the first release candidate for NCI DEV. They would only need the LexEVS core API initially (no remote service). Priority for sprint 28 will be to get LexEVS API deployed to NCI DEV. CTS2 changes have a lower priority. | ||||||||||
LexEVS Compatibility
| Cory will add notes to the wiki that describes the changes. | ||||||||||
Feature request to get qualifiers on properties (Metathesaurus)
| CTS2 needed to be upgraded (Lucene dependencies) for 6.4. We will need CTS2 services for both LexEVS 6.4 and LexEVS 6.3. CTS2 service for LexEVS 6.4 can be used by end users instead of the CTS2 service for LexEVS 6.3. There are no API changes. However, there are dependency changes for the CTS2 services. This results in the CTS2 service being dependent on 6.4 and will not be able to talk to LexEVS 6.3. Larry suggested getting the CTS2 service for LexEVS 6.3 up the tiers prior to CTS2 service for 6.4. It was decided that the CTS2 service for 6.3 will be deployed up to PROD independent of the CTS2 service for 6.4. The CTS2 service for 6.4 will be deployed with LexEVS 6.4. | ||||||||||
PTE for CI and DEV environment discussion
| PTE for CI server request questions
Jacob will need to make a VM request for our Jenkins instance.
PTE for LexEVS
| ||||||||||
LexEVS External Users | Nothing to note. |
...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...