Each new release has different feature upgrades, not all require a complete tear down and reinstallation of the system. Additionally, uninstalling the system mean that org will lose all of their data (model configs, user database, audit logs, forecast viewer products, model data, etc.) every time they want to upgrade to a new version. Need to design scripts to smartly identify which parts of the system to "save" and which to reinstall/upgrade. For example, maybe a new release means just needing to reinstall the AMI.
Acceptance Testing
List input data types and sources.Describe tests required for new functionality.
Time Estimate
Estimate the amount of work required here.Issues should represent approximately 1 to 3 days of work.
Sub-Issues
Consider breaking the new feature down into sub-issues.
[ ] Add a checkbox for each sub-issue here.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Define the Metadata
Assignee
[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required
Labels
[ ] Select component(s)
[ ] Select priority
Projects and Milestone
[ ] Select Project
[ ] Select Milestone as the next official version or Backlog of Development Ideas
New Feature Checklist
[ ] Complete the issue definition above, including the Time Estimate and Funding source.
[ ] Fork this repository or create a branch of develop.
Branch name: feature_<Issue Number>/<Description>
[ ] Complete the development and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s), Project, and Development issue
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
Describe the New Feature
Each new release has different feature upgrades, not all require a complete tear down and reinstallation of the system. Additionally, uninstalling the system mean that org will lose all of their data (model configs, user database, audit logs, forecast viewer products, model data, etc.) every time they want to upgrade to a new version. Need to design scripts to smartly identify which parts of the system to "save" and which to reinstall/upgrade. For example, maybe a new release means just needing to reinstall the AMI.
Acceptance Testing
List input data types and sources. Describe tests required for new functionality.
Time Estimate
Estimate the amount of work required here. Issues should represent approximately 1 to 3 days of work.
Sub-Issues
Consider breaking the new feature down into sub-issues.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Define the Metadata
Assignee
Labels
Projects and Milestone
New Feature Checklist
feature_<Issue Number>/<Description>feature <Issue Number> <Description>