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

Create the MET-11.0.2 release #2496

Closed
5 of 19 tasks
jprestop opened this issue Mar 30, 2023 · 0 comments · Fixed by #2497 or #2500
Closed
5 of 19 tasks

Create the MET-11.0.2 release #2496

jprestop opened this issue Mar 30, 2023 · 0 comments · Fixed by #2497 or #2500
Assignees
Labels
component: release engineering Release engineering issue priority: blocker Blocker requestor: METplus Team METplus Development Team type: task An actionable item of work

Comments

@jprestop
Copy link
Collaborator

jprestop commented Mar 30, 2023

Describe the Task

Create the MET-11.0.2 bugfix release

Time Estimate

2 hours

Sub-Issues

Consider breaking the task down into sub-issues.
None needed.

Relevant Deadlines

3/30/23 or 3/31/23

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

  • [s] 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 Development 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.
@jprestop jprestop added type: task An actionable item of work priority: blocker Blocker component: release engineering Release engineering issue requestor: METplus Team METplus Development Team labels Mar 30, 2023
@jprestop jprestop added this to the MET 11.0.2 (bugfix) milestone Mar 30, 2023
@jprestop jprestop self-assigned this Mar 30, 2023
@jprestop jprestop moved this from 📋 Backlog to 🔖 Ready in Coordinated METplus-5.0 Support Mar 30, 2023
@jprestop jprestop linked a pull request Mar 30, 2023 that will close this issue
15 tasks
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in Coordinated METplus-5.0 Support Mar 30, 2023
jprestop added a commit that referenced this issue Mar 31, 2023
* Updated release notes for 11.0.2 bugfix release

* Updating date and version

* Update docs/Users_Guide/release-notes.rst

Co-authored-by: John Halley Gotway <[email protected]>

* Update docs/Users_Guide/release-notes.rst

Co-authored-by: John Halley Gotway <[email protected]>

* Update date, and version number in new location

---------

Co-authored-by: John Halley Gotway <[email protected]>
@jprestop jprestop linked a pull request Mar 31, 2023 that will close this issue
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: release engineering Release engineering issue priority: blocker Blocker requestor: METplus Team METplus Development Team type: task An actionable item of work
Projects
Development

Successfully merging a pull request may close this issue.

1 participant