As WRES team, I would like to identify a candidate for github Release v6.27, test it, and if it passes, deploy it; candidate RC1: 74b8415b4960c458f786a4a6ede33d6ea6d76fcf wres-20241018-74b8415.zip

[epag]

• 1 - Update vulnerable (or more) libraries in WRES applications (use gradle task and/or inspect build.gradle vs repositories)
• 2 - Tag a commit as staging to kick off pre-release workflow (Pre-release github action)
• 3 - Nominate a commit that has passed the pre-release workflow (Pre-release github action)
• 4 - Check nominated version passes live external services tests (Results sent via emails)
• 5 - Check nominated version passes full system tests (Results sent via emails)
• 6 - Test candidate with 900 series system tests (WRES Test VM or PC)
• 7 - Test migration from scratch (new database instance) - migration succeeds with no issues
• 8 - Test candidate by doing database migration from previous release db with half of system test data to this release with no issues
• 9 - Test candidate with identified alpha (internal) User Acceptance Tests (-ti)
• 10 - Test candidate as a standalone.
• 11 - Push yml files changed
• 12 - Tag the commits that produced the release that passed everything and was already deployed to -prod
• 13 - Update database documentation in wiki
• 14 - Update user documentation
• 15 - Close GitHub tickets actually completed in this release and move tickets not completed to backlog

[epag]

I am going to temporarily turn off the staging deployment job and go through the staging deploy

[epag]

Staging checks passed

[epag]

Nominated
commit 74b8415
wres-20241018-74b8415.zip

[epag]

Passed external and extended tests

[epag]

Doing 900 series

[epag]

900 series pass in a reasonable time

wres.2024-10-18.log

[epag]

Going to upload to staging now. Will need some help doing UAT, but the full deploy is going to have to wait to monday

[epag]

deployed to staging, ready for UAT

[epag]

Finished UAT

[epag]

Standalone testing looks good as well