CASA Software Engineering Project: Design a CASA Package Contents Reporting System

Design and build a system for recording and reporting the contents of CASA packages, including reporting for users (public version numbers, new features, bug fixes, known issues, etc.) and developers (internal version numbers, change control data, file checksums, etc.).

Status: See CAS-5475.

---

Team

• ScottRankin

Customers

• CASA Developers

Collaborators

• DarrellSchiebel
• JimJacobs

Plan

(Note: replace this note with an outline of the plan to complete this project. Do not list detailed steps. These will be tracked in Jira as necessary.)

Deliverables

(Note: replace this note with a list of deliverables for this project (docs, user's guides, etc.). Do not include documents listed below in this list. As the project progresses, convert list into links to deliverables.)

Requirements

Reports to Users

• Package version
• Quality ( test | stable | prerelease | release )
• New features
• Bug fixes
• Knows issues

Features, fixes, and known issue reports must include links to Jira tickets.

Reports to Developers

• Proto package version
• Change control repositories and versions package was built from
• Build hosts
• Check of file checksums - to detect corrupted packages.

Data collection

Collect data at packaging time

• Collect feature, bug fix, and known issue data from Jira and Subversion where possible.
• Compute file checksum data at packaging time.

Design

TBD

Implementation

(Note: replace this note with a one paragraph summary of the implementation for this project, a short bullet list of implementation details, or link(s) other pages documenting the implementation for this project. Often, this will be a bullet list including the location for any source code in change control and any user accounts or computers required by this project.)

Tasks

Project tasks are tracked with Jira sub-tasks under this project's master task. See CAS-5475.

-- ScottRankin - 2013-08-06