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.1.0-beta2 release #2517

Closed
7 of 20 tasks
JohnHalleyGotway opened this issue Apr 21, 2023 · 4 comments · Fixed by #2522, #2530 or #2534
Closed
7 of 20 tasks

Create the MET-11.1.0-beta2 release #2517

JohnHalleyGotway opened this issue Apr 21, 2023 · 4 comments · Fixed by #2522, #2530 or #2534
Assignees
Labels
component: release engineering Release engineering issue priority: blocker Blocker requestor: METplus Team METplus Development Team type: task An actionable item of work
Milestone

Comments

@JohnHalleyGotway
Copy link
Collaborator

Describe the Task

Create the MET-11.1.0-beta2 development release. Remember to create a new discussion for testing the beta2 release, as we did for beta1 with dtcenter/METplus#2039.

Time Estimate

2 hours

Sub-Issues

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

Relevant Deadlines

Should be created on 2/28/23.

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 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.
@JohnHalleyGotway JohnHalleyGotway added type: task An actionable item of work priority: blocker Blocker component: release engineering Release engineering issue requestor: METplus Team METplus Development Team labels Apr 21, 2023
@JohnHalleyGotway JohnHalleyGotway added this to the MET 11.1.0 milestone Apr 21, 2023
@JohnHalleyGotway JohnHalleyGotway self-assigned this Apr 21, 2023
@JohnHalleyGotway JohnHalleyGotway moved this from 📋 Backlog to 🏗 In progress in MET-11.1.0 Development Apr 23, 2023
@JohnHalleyGotway JohnHalleyGotway linked a pull request Apr 23, 2023 that will close this issue
15 tasks
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in MET-11.1.0 Development Apr 23, 2023
@JohnHalleyGotway
Copy link
Collaborator Author

Reopening this issue on 4/28/23 since we're recreating this beta2 release to include one more fix.

PR #2509 for issue #2285 caused unexpected differences in the METplus use cases. Issue #2525 fixes the underlying problem in MET. Recreating beta2 to include it.

@github-project-automation github-project-automation bot moved this from ✅ Done to 🏗 In progress in MET-11.1.0 Development Apr 28, 2023
@JohnHalleyGotway
Copy link
Collaborator Author

Merging PR #2529 for issue #2525 triggered this GHA run in METplus. One difference is flagged in a short-range use case test:

ERROR: Some differences were found
NetCDF diff
A:/data/truth/short_range/GenEnsProd_fcstHRRR_fcstOnly_SurrogateSevere/short_range/surrogate_severe_calc/surrogate_severe_20200205_036V_regrid.nc
B:/data/output/short_range/GenEnsProd_fcstHRRR_fcstOnly_SurrogateSevere/short_range/surrogate_severe_calc/surrogate_severe_20200205_036V_regrid.nc

I expect @georgemccabe to confirm that this Gen-Ens-Prod difference is a known issue unrelated to these python changes, and that we can proceed with re-creating the MET-11.1.0-beta2 release.

@JohnHalleyGotway JohnHalleyGotway linked a pull request Apr 28, 2023 that will close this issue
15 tasks
@JohnHalleyGotway
Copy link
Collaborator Author

Re-created 11.1.0-beta2 release on 4/28/23.

@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in MET-11.1.0 Development Apr 28, 2023
@JohnHalleyGotway
Copy link
Collaborator Author

Re-creating the 11.1.0-beta2 release AGAIN on 5/5/23 to include the fix for issue #2531 which was preventing it from compiling on Hera.

@github-project-automation github-project-automation bot moved this from ✅ Done to 🏗 In progress in MET-11.1.0 Development May 5, 2023
@JohnHalleyGotway JohnHalleyGotway linked a pull request May 5, 2023 that will close this issue
15 tasks
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in MET-11.1.0 Development May 5, 2023
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
No open projects
Status: Done
1 participant