Attendees
Name | Role |
---|---|
Action Items
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
. |
Progress
Area of Interest | Details |
---|---|
LexEVS 6.3 | The SCM team was working on the AHP setup but found an issue with the build where the CTS framework was not found. The Mayo team is working with them to get the build fixed. |
Report Writer | Need a decision on where this functionality is going to go to start creating trackers and scope document. |
Term Browser | Kim and Tin are working on the setup of the automated testing environment for QA. We are making progress but Kim is working through a couple of issues. During the test run we found a couple of possible bugs on the stage environment that we are investigating. |
Meta Download Validation App | |
Term Suggestion Form |
|
NCIm Browser |
|
JIRA Issues
Issue Number | Description | Status |
---|---|---|
NCITERM-660 | UI Testing Utility. | Resolved a selenium driver threading issue. Provided the latest jar files developed to the QA team. Provided technical support to the QA team to set up the UI test environment. |
NCITERM-676 | Remove VKC link from Mapping page. | Implemented |
NCITERM-679 | Terms with apostrophes return no results. | Identified the root cause of the underlying issue. A bug was accidentally introduced by a method implemented earlier in responding to the potential SQL injection attack. |
NCITERM-677 | Add ncicp:subsource-name field to the display of FULL_SYN in Synonym tab. | Developed a method for implementing the above feature request. An explicit requirement is yet to be determined by the user group. |
Schedule Changes
# | Description | Due Date | Resources | Notes | Risks | Mitigation |
---|---|---|---|---|---|---|
Planned Activities
Area of Interest | Details |
---|---|
Report Writer | Develop Project plan for 2.1 release. |
Term Browser 2.7 Release | Scheduling the release and start development. |
Risks, Issues, Dependencies
Risks
# | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
---|---|---|---|---|---|---|---|---|
04/10/14 | Deployments have been taking long periods of time. There is a lot of overhead getting through the iters | H | H | Speaking with members of the QA team to find ways to streamline the testing/deployment process | Finding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels. | |||
Issues
# | Opened Date | Description | Impact | Assigned | Status |
---|---|---|---|---|---|
7/17/2014 | Deployment of software, even small upgrades, have been a lengthy process. | This especially affects smaller releases in which there are security or bug fixes. | The Agile practices migration have been put on hold for now. | ||
09/10/2014 | Getting the environment in place for the Mayo trip to NCI. | Need to get each of the environment (DEV,QA,Stage) in place before the Mayo trip on September 22nd. We are currently one week behind. The impact is that the Mayo developer will be onsite to work on the deployments and the tiers will not be in place. | Currently we only have the DEV environment setup for the LexEVS API> | ||
Dependencies
Opened Date | Description | Assigned |
---|---|---|
. | ||