Check update process for 6.0.2

[ccordoba12]

Given that the changes in PR #22598 are not so simple, I think we should manually check the update process is working as expected.

For that, I propose the following:

• With the nightly installers for the day before, click on the Check for updates... menu entry after the 6.0.2rc1 Github release is published but before the installers are generated. This should give no error and offer no update either.
• After the installers are uploaded, and also using the nightly installers, check the update process between them and rc1 is working.

@mrclary, are there other checks you think we should run before releasing 6.0.2?

[mrclary]

@ccordoba12, I think that is the best we can do. I don't think anything else needs to be tested.

I think that we'll need to coordinate our check for update with the Github release since we will have a short time window in which to test it:

• Linux: < 5min
• macOS: ~8-12min
• Windows: ~27min

Perhaps a zoom/discord call? If everyone installs the latest nightly before the call, then we can be ready to test the check-for-update as soon as @dalthviz publishes the release while on the call.

[ccordoba12]

Perhaps a zoom/discord call? If everyone installs the latest nightly before the call, then we can be ready to test the check-for-update as soon as @dalthviz publishes the release while on the call.

Agreed, that's a good idea. What do you think @dalthviz?

[dalthviz]

Sure 👍