-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Check update process for 6.0.2 with a rc (6.0.2rc1) #22685
Comments
@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:
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. |
Sure 👍 |
Just in case 6.0.2rc1 is now available over PyPI (https://pypi.org/project/spyder/6.0.2rc1/) and also created the PR to update the conda-forge recipe (conda-forge/spyder-feedstock#195) |
So GitHub release for 6.0.2rc1 was created (https://github.com/spyder-ide/spyder/releases/tag/v6.0.2rc1) and manual testing for the improvements to the update mechanism were successful 🎉 So I would say this should be closed now, right @ccordoba12 @mrclary ? |
I'm double-checking the update process, so standby... |
Okay, everything looks good on my end. rc1 updated successfully. |
I can confirm that the update proceeded without problems on Linux too. @dalthviz, could you check that on Windows? If things are working as expected, then close this issue. |
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:
Check for updates...
menu entry after the6.0.2rc1
Github release is published but before the installers are generated. This should give no error and offer no update either.@mrclary, are there other checks you think we should run before releasing 6.0.2?
The text was updated successfully, but these errors were encountered: