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

Smoke test update notice #1079

Open
wants to merge 1 commit into
base: next-release
Choose a base branch
from
Open

Smoke test update notice #1079

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion contribute/en/Release-Process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -310,7 +310,14 @@ Current state: <!-- Planning|Translations (beta)|Code freeze (rc)|Released -->
- [ ] Update the version number in `Jamulus.pro` and add the release date to the Changelog header and commit.
- [ ] Wait for the release build to complete.
- [ ] Contact emlynmac for signing on macOS and upload signed binary [from his](https://github.com/emlynmac/jamulus/releases/) repo [to ours](https://github.com/jamulussoftware/jamulus/releases).
- [ ] Do a smoke test for Windows/Mac/Linux -- Do the binaries start/connect properly? Can earlier Jamulus versions properly connect to a server based on the new release?
- [ ] Do a smoke test for Windows/Mac/Linux
- [ ] Do the binaries start/connect properly?
- [ ] Can earlier Jamulus versions properly connect to a server based on the new release?
- [ ] Do a smoke test of the upgrade notification (do this _very quickly_)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any better way to test this instead of testing in production?

Copy link
Contributor Author

@pljones pljones Dec 29, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Part of the point is to check that an old version does find the production update.

- [ ] Install the release build on _one_ of the update notification Servers
- [ ] Run the _previous release_ (not an intermediate) build of GUI Client and Server
- [ ] Check the update notice is displayed correctly
- [ ] Revert the update notification Server to the previous release
- [ ] [Force tag that tag as `latest` and push.](https://jamulus.io/contribute/Release-Process#if-this-is-a-proper-release-move-the-latest-tag)
- [ ] [Upload the artifacts to SourceForge and set defaults](https://jamulus.io/contribute/Release-Process#upload-binaries-to-sourceforge).
- [ ] Update download links on the website by editing `_config.yml` in `next-release`
Expand Down
Loading