Sprint 120 Progress Summary

Owned by Deepthi Rodrigues (Unlicensed)
Last updated: Dec 06, 2013 by Greg Turner (Unlicensed)
2 min read

Sprint Review + Planning

Nov 18 - Dec 2, 2013

 

Executive Summary

Overall Status

Sprint status is excellent. The Product team had pointed and prioritized the following themes and tasks for Sprint 120 comprising 15 points. The team completed 15 points.

  • A testing improvement ticket (CONN-712) was added late in the sprint for one story point, the one story is not reflected in the JIRA screen print below where it only reflects 14 total story points.

Note - The velocity was less than prior sprints due to the holidays and personal time off

Burndown

(We are having some issues with JIRA burndown charts and will have this chart updated for Sprint 120 as soon as this issue is resolved)


Sprint Themes and related tickets for Sprint 120:

  • Partner and Community support
    • Forum discussions
    • Support community with Release 4.2 deployments and questions
      • Research related to issues encountered during large payload testing in CMS Environment and support CMS with 4.2 installation(CONN-697, CONN-703, CONN-708)

        • The CONNECT Product team was able to isolate the issue in the ESMD custom adapter and figured out the ESMD adapter uses Asynchronous mechanism (Using Threads) to process the DS request, which terminates the HTTP DS request before the attachment data is read from the request stream , causing file payload truncation or in some cases zero payload.

          We provided a solution to read the full Payload from the DS request stream and pass the full payload data to the ESMD adapter for continued processing.

          Based on this effort, we also confirmed the following:
          1. CONNECT 4.2 large payload support feature works as designed
          2. CONNECT 4.2 is Interoperable with prior versions of CONNECT
          3. CONNECT 4.2 supports large payloads of 1 GB data files and larger

      • DIL testing for CONNECT (CONN-704)

      • Install and test HIEOS with CONNECT codebase (CONN-668)
      • Investigate why xmlsec-1.5.3.jar is packaged within each web application(CONN-709)
      • Set up a JUDDI implementation, to increase test coverage in interoperability testing (CONN-712)
        • Provides the ability to use a UDDI instance for interoperability testing and can be expanded to other uses in the future.
  • Security scan analysis
    • Addressed Path manipulation scan results(CONN-675/CONN-701)
    • Addressed Null dereference Fortify scan results(CONN-676)
    • Addressed Denial of Service: Parse Double Fortify scan results(CONN-682)
    • Security scan Issues above were fixed and validation/regression tests were executed successfully
    • As a CONNECT developer, I want to include the security plugin for findbugs, to help identify security vulnerabilities in CONNECT.(CONN-710)
  • Direct enhancements
    • Provide the ability to create MDN Notification request header via Sylpheed (CONN-700) to facilitate testing.
  • Ongoing Custodial Agent Duties

Prioritized JIRA Planning Board of Committed User Stories for Sprint 120

(https://issues.connectopensource.org/secure/RapidBoard.jspa?rapidView=1&view=planning&versions=visible)

 

Related Files