Skip to content

As the WRES team, I would like to identify a candidate for github Release v7.4, test it, and if it passes deploy it; candidate RC1: 72c4c1ca639372311f08d543125758abfbcc1cb412c9808335bc172a281dd09e wres-20260327-03cd3ae.zip #774

@HankHerr-NOAA

Description

@HankHerr-NOAA
  • 1 - Tag a commit as staging to kick off pre-release workflow (Pre-release github action; this tests db migration)
  • 2 - Nominate a commit that has passed the pre-release workflow (Pre-release github action)
  • 3 - Initiate staging release (initiate-release-deployment Jenkins workflow; emails will report test results for external service, system tests, and 900 series)
  • 4 - Test candidate with identified alpha (internal) User Acceptance Tests (-ti)
  • 5 - Test candidate as a standalone.
  • 6 - Push yml files changed
  • 7 - Tag the commits that produced the release that passed everything and was already deployed to -prod
  • 8 - Update database documentation in wiki
  • 9 - Update user documentation (search for wiki entry required tag) https://github.com/NOAA-OWP/wres/issues?q=label%3A%22wiki%20entry%20required%22
  • 10 - Close GitHub tickets actually completed in this release and move tickets not completed to backlog

Metadata

Metadata

Assignees

No one assigned

    Labels

    deploymentWork related to deployments

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions