CASA Software Engineering Project: Standardize Casa Package Contents
CASA package contents is inconsistent between OS X dmgs, Linux tar, and Enterprise Linux rpms, and none of these follow UNIX conventions as consistently as they could. This unnecessarily increases the work required by users and developers to work with CASA on different platforms.
Redesign all CASA packages to contain
- A consistently organized core package following UNIX conventions, and
- platform specific extensions to that core as required.
(Note: List everyone working on the project, customers, and anyone the project team may need to coordinate with (collaborators).)
Members - actively working on this project.
Customers - providing requirements.
Collaborators - may assist with project, but are not directly responsible for deliverables.
(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.)
(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.)
(Note: replace this note with a one paragraph summary of the design for this project, a short bullet list of design details, or links other pages documenting the design for this project.)
(Note: replace this note with a one paragraph summary of the implementation for this project, a short bullet list of implementation details, or links 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.)
Project tasks are tracked with Jira sub-tasks under this project's master task. See CAS-6306