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-rc2 release #2620

Closed
7 of 20 tasks
JohnHalleyGotway opened this issue Jul 24, 2023 · 0 comments · Fixed by #2622
Closed
7 of 20 tasks

Create the MET-11.1.0-rc2 release #2620

JohnHalleyGotway opened this issue Jul 24, 2023 · 0 comments · Fixed by #2622
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
Milestone

Comments

@JohnHalleyGotway
Copy link
Collaborator

Describe the Task

Create the MET-11.1.0-rc2 development release. Remember to update the release candidate acceptance testing discussion with details and coordinate with the UK MetOffice to test LAEA functionality.

Time Estimate

2 hours.

Sub-Issues

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

Relevant Deadlines

Monday 7/24/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 CYCLE 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 alert: NEED ACCOUNT KEY Need to assign an account key to this issue component: release engineering Release engineering issue requestor: METplus Team METplus Development Team priority: high High Priority labels Jul 24, 2023
@JohnHalleyGotway JohnHalleyGotway added this to the MET 11.1.0 milestone Jul 24, 2023
@JohnHalleyGotway JohnHalleyGotway self-assigned this Jul 24, 2023
@JohnHalleyGotway JohnHalleyGotway moved this from 📋 Backlog to 🔖 Ready in MET-11.1.0 Development Jul 24, 2023
@JohnHalleyGotway JohnHalleyGotway moved this from 🔖 Ready to 🏗 In progress in MET-11.1.0 Development Jul 24, 2023
@JohnHalleyGotway JohnHalleyGotway linked a pull request Jul 24, 2023 that will close this issue
15 tasks
JohnHalleyGotway added a commit that referenced this issue Jul 24, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in MET-11.1.0 Development Jul 24, 2023
@JohnHalleyGotway JohnHalleyGotway removed the alert: NEED ACCOUNT KEY Need to assign an account key to this issue label Oct 17, 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
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant