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 METcalcpy-3.0.0-rc1 release #410

Closed
9 of 23 tasks
jprestop opened this issue Nov 13, 2024 · 0 comments · Fixed by #411
Closed
9 of 23 tasks

Create the METcalcpy-3.0.0-rc1 release #410

jprestop opened this issue Nov 13, 2024 · 0 comments · Fixed by #411
Assignees
Labels
component: release engineering Release engineering issue priority: high High Priority requestor: METplus Team METplus Development Team type: task An actionable item of work

Comments

@jprestop
Copy link
Collaborator

Describe the Task

Create the METcalcpy-3.0.0-rc1 development release.

Remember to:

Update dtcenter/METplus#2342 discussion to request external acceptance testing of new features.

Time Estimate

3 hours

Sub-Issues

Consider breaking the task down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

20241113

Funding Source

2782544

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as a METcalcpy-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
  • For a METcalcpy-X.Y.Z version, select the METcalcpy-X.Y.Z Development project

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.
  • Add any new Python packages to the METplus Components Python Requirements table.
  • 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 issue
    Select: Milestone as the next official version
    Select: METcalcpy-X.Y.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.
@jprestop jprestop added priority: high High Priority type: task An actionable item of work component: release engineering Release engineering issue requestor: METplus Team METplus Development Team labels Nov 13, 2024
@jprestop jprestop added this to the METcalcpy-3.0.0 milestone Nov 13, 2024
@jprestop jprestop self-assigned this Nov 13, 2024
@jprestop jprestop moved this to 🏗 In progress in METplus-Analysis-6.0.0 Development Nov 13, 2024
jprestop added a commit that referenced this issue Nov 13, 2024
jprestop added a commit that referenced this issue Nov 13, 2024
@jprestop jprestop linked a pull request Nov 13, 2024 that will close this issue
15 tasks
jprestop added a commit that referenced this issue Nov 13, 2024
* Per #410, updating version and date

* Per #410, update release notes

* Update docs/Users_Guide/release-notes.rst

Co-authored-by: George McCabe <[email protected]>

---------

Co-authored-by: George McCabe <[email protected]>
@github-project-automation github-project-automation bot moved this from 🏗 In progress to 🏁 Done in METplus-Analysis-6.0.0 Development Nov 13, 2024
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: high High Priority requestor: METplus Team METplus Development Team type: task An actionable item of work
Projects
Status: 🏁 Done
Development

Successfully merging a pull request may close this issue.

1 participant