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.

Sign up for GitHub

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

Jump to bottom

Create the METplotpy v3.1.0-beta1 release #484

Closed
23 tasks
bikegeek opened this issue Jan 22, 2025 · 0 comments · Fixed by #485
Closed
23 tasks

Create the METplotpy v3.1.0-beta1 release #484

bikegeek opened this issue Jan 22, 2025 · 0 comments · Fixed by #485
Assignees
@bikegeek
Labels
alert: NEED ACCOUNT KEY Need to assign an account key to this issue component: release engineering Release engineering issue priority: high High Priority requestor: METplus Team METplus Development Team type: task An actionable item of work
Milestone
METplotpy-3.1.0

Comments

@bikegeek
Copy link
Collaborator

Replace italics below with details for this issue.

Describe the Task

Provide a description of the task here.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

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

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

Milestone and Projects

  • Select Milestone as a METplotpy-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
  • For a METplotpy-X.Y.Z version, select the METplotpy-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: METplotpy-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.
@bikegeek bikegeek added alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle alert: NEED MORE DEFINITION Not yet actionable, additional definition required type: task An actionable item of work labels Jan 22, 2025
@bikegeek bikegeek added this to the METplotpy-3.1.0 milestone Jan 22, 2025
@bikegeek bikegeek self-assigned this Jan 22, 2025
jprestop added a commit that referenced this issue Jan 23, 2025
@jprestop
Per #484, Added header line for beta release notes; Added capitalization
1c6eae8
jprestop added a commit that referenced this issue Jan 23, 2025
@jprestop
Per #484, updating release date
8b71272
jprestop added a commit that referenced this issue Jan 23, 2025
@jprestop
Per #484, updating release date
e5b7511
@jprestop jprestop linked a pull request Jan 23, 2025 that will close this issue
Feature 484 v3.1.0 beta1 #485
Merged
15 tasks
@jprestop jprestop added priority: high High Priority component: release engineering Release engineering issue requestor: METplus Team METplus Development Team and removed alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle labels Jan 23, 2025
bikegeek added a commit that referenced this issue Jan 23, 2025
@bikegeek @jprestop
Feature 484 v3.1.0 beta1 (#485)
c6d2ade 
* update for beta1

* updated for beta1

* Per #484, Added header line for beta release notes; Added capitalization

* Per #484, updating release date

* Per #484, updating release date

---------

Co-authored-by: Julie Prestopnik <jpresto@ucar.edu>
@github-project-automation github-project-automation bot moved this to 🩺 Needs Triage in METplus-6.1.0 Development Jan 28, 2025
@JohnHalleyGotway JohnHalleyGotway moved this from 🩺 Needs Triage to 🏁 Done in METplus-6.1.0 Development Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bikegeek bikegeek

Labels
alert: NEED ACCOUNT KEY Need to assign an account key to this issue component: release engineering Release engineering issue priority: high High Priority requestor: METplus Team METplus Development Team type: task An actionable item of work
Projects
METplus-6.1.0 Development
Status: 🏁 Done
Milestone
METplotpy-3.1.0
Development

Successfully merging a pull request may close this issue.

Feature 484 v3.1.0 beta1 dtcenter/METplotpy
2 participants
@bikegeek @jprestop