Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tidy up documentation for Gen-Ens-Prod #2098

Closed
21 tasks
DanielAdriaansen opened this issue Mar 14, 2022 · 0 comments · Fixed by #2100
Closed
21 tasks

Tidy up documentation for Gen-Ens-Prod #2098

DanielAdriaansen opened this issue Mar 14, 2022 · 0 comments · Fixed by #2100
Assignees
Labels
component: documentation Documentation issue MET: Ensemble Verification priority: low Low Priority type: task An actionable item of work
Milestone

Comments

@DanielAdriaansen
Copy link
Contributor

Replace italics below with details for this issue.

Describe the Task

Small changes to Gen-Ens-Prod documentation while noted during training development

Time Estimate

1 hour

Sub-Issues

Consider breaking the task down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys 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
  • Select requestor(s)

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

Task Checklist

See the METplus Workflow for details.

  • 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 unit 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) and Linked issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: documentation Documentation issue MET: Ensemble Verification priority: low Low Priority type: task An actionable item of work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants