March 11th - March 24th, 2013
Executive Summary
Overall Status
| Info |
|---|
Sprint status is Excellentgood. The team accomplished almost all of the thematic work defined for the sprint. |
Burndown
Cumulative Flow
Sprint Themes
The Product team pointed and prioritized the following themes and tasks for Sprint 103 comprising 23 points.
Proposed Themes:
24 points. The team completed 19 of the 24 total points for this sprint.
- 4.0 Partner and Community Support
- CONN-310 - standardize recommended java options (heap sizes, perm sizes) across installation instructions
- SSA 4.0 install on WAS.
- CONN-288 - Provide support for SSA and their efforts to download and install CONNECT 4.0 into their development environment.
- CMS-CCSQ 4.0 install on WL 11g or 12c.
- CONN-290 - As a CONNECT adopter, I want support installing and deploying CONNECT 4.0 successfully on Webogic 11g so that I can validate that it works in my preferred environment.CMS-OFM 4.0 install on WAS 7 JDK 1.7
- CMS-OFM 4.0 install on WAS 7 JDK 1.7.
- CONN-279 - As a CONNECT adopter, I want CONNECT 4.0 to be tested on WebSphere 7.x to validate whether CONNECT will work in my preferred environment. (See also CONN-313 for some additional analysis)
- Respond to IHS re the Direct ticket.
- CONN-278 As a CONNECT adopter, I would like assistance installing and configuring "Direct only" for CONNECT 4
- CONN-183 - Missing DIRECT_ERROR event in use case (CONN-279)
- Community support through forum responses and guidance
- Direct-A-Thon).
- CONN-74- As a CONNECT adopter/developer I want a clean property file (gateway.properties) so that there is no confusion with regards to the unused properties or default values.
- CONNECT 4.1
- JBoss Support - Another strategic application server the community wanted CONNECT 4.0 tested with was JBoss. JBoss provides an open source app server that supports FIPS requirements
- CI and Build Improvements
- A key goal for 4.1 was to increase the JUnit code coverage and reduce FindBugs errors for the Connect Core Library.
- The initial target was to remove all possible bugs from the library using the FindBugs tool and increase both our line and branch coverage by 20% - See Link to code coveragehttps://developer.connectopensource.org/display/CONNECT40/4.1+Code+Coverage
- Multi-Spec QD / RD End point enhancement for DoD/SSA (pending DE&I approval)
- Installation improvements through community engagement
- Continued development of a robust CI and automated test environment
- JBoss - (CONN-25) in the Ordered features list
- 4.0.1 Patch Release - patch release test and make enhancements to 4.0 available to communityResolved Support tickets
- CONN-301 - As a CONNECT user, I want the Direct feature to work out of the box on binary installations, so I can set up Direct more easily.
- CONN-319 - Fix testMpi resource so it doesn't always get updated
- CONN-292 - CONNECTSamlAssertionValidator Logic needs review
- CONN-280 - PatientDB implementation does not work
- CONN-92 - Remove NHINC_PROPERTIES_DIR environment variable
- CONN-40 - Audit Log Transforms (PD) throws exception in server log
- CONN-37 - NPI SAML attribute is not supported in CONNECT
- CONN-61 - GUIs deployed in the EAR (GF) cause the admin console to misbehave after restart
- Release prep and other tasks
- CONN-299 - Release test plan
- CONN-307 – Interop testing
- CONN-305 – Re-verification testing
- CONN-304-- Regression testing
- CONN-295 - Interop: Update harness for repeatable Ldev11 tests
- CONN-297 - merge all fixes in CONNECT_integration into branch 4.0-integration in order to prepare to release 4.1
- CONN-244 - Create QA Mail Server
Prioritized JIRA Planning Board of Committed User Stories for Sprint
...
103
(https://issues.connectopensource.org/secure/VersionBoard.jspa?selectedProjectId=10140)
Related Files
- Sprint 103 review notes - Notes about the work completed in s103. (Also includes work planned for s104)
- Sprint 103 planning notes - Notes about the work planned in s103. (Also includes work completed for s102)
- Sprint 103 code tag
- JIRA. See Sprint 103