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 METplotpy-3.0.0-beta6 release #469

Open
8 of 23 tasks
jprestop opened this issue Oct 15, 2024 · 0 comments · Fixed by #470
Open
8 of 23 tasks

Create the METplotpy-3.0.0-beta6 release #469

jprestop opened this issue Oct 15, 2024 · 0 comments · Fixed by #470
Assignees
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

Comments

@jprestop
Copy link
Contributor

Describe the Task

Create the METplotpy-3.0.0-beta6 development release.

Remember to:

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

Check with @bikegeek to confirm there are no necessary upgrade instructions.

Time Estimate

3 hours

Sub-Issues

Consider breaking the task down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

Release during before 10/18/24, preferably by 10/16/24.

Funding Source

TBD

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.
@jprestop jprestop added type: task An actionable item of work priority: high High Priority 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 labels Oct 15, 2024
@jprestop jprestop added this to the METplotpy-3.0.0 milestone Oct 15, 2024
@jprestop jprestop self-assigned this Oct 15, 2024
@jprestop jprestop linked a pull request Oct 16, 2024 that will close this issue
15 tasks
bikegeek added a commit that referenced this issue Oct 17, 2024
* Per #469, update version and date information

* Per #469, updating release instructions

* Per 69, correcting typo

* Per 69, adding None to drop boxes for consistency

* Enclose call to the METcalcpy sum_stat module's calculate_statistic to capture error and log appropriately for success and failure

* Updated metplus-action-release-checksum version

---------

Co-authored-by: bikegeek <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Status: 🟢 Ready
Development

Successfully merging a pull request may close this issue.

1 participant