updated release cycle and added update checklist #5841
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
First changes for the Upgrading Galaxy GTN that is outdated. Added the first draft for a checklist Galaxy admins could use when upgrading their instance. Updating this GTN is not completed.
Contributor
Author
|
To be completed after we've upgraded to v25.0 and put the upgrade checklist in practice on more time. |
nsoranzo
reviewed
Nov 13, 2025
Contributor
Author
|
Not sure if checkboxes don't work or my local deployment is just wonky (currently ignoring some warnings and conflicts): |
nsoranzo
reviewed
Dec 3, 2025
Co-authored-by: Nicola Soranzo <[email protected]>
nsoranzo
reviewed
Dec 10, 2025
| > - Assess if current (automatic) backup system needs to be suspended or updated | ||
| > - Perform a full backup of the relevant databases (PostgresDB, SQLite,...) | ||
| > - Verify that backups are complete and functional by reinstating backups in a duplicate setup | ||
| > - Make a regression plan on how to roll back to the original, pre-upgrading state in case the upgrade fails |
Member
There was a problem hiding this comment.
Do you have an example of a regression plan? It would be interesting to include that as well.
Contributor
Author
There was a problem hiding this comment.
Yes I could include it, I think from that point maybe it's better to dedicate a whole section on this instead of inside a 'hands on' box? Will help me restructure/update the rest of the tutorial as well I believe.
Co-authored-by: Nicola Soranzo <[email protected]>
Co-authored-by: Nicola Soranzo <[email protected]>
Co-authored-by: Nicola Soranzo <[email protected]>
Co-authored-by: Nicola Soranzo <[email protected]>
Co-authored-by: Nicola Soranzo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First changes for the Upgrading Galaxy GTN that is currently outdated.
The main reason for this PR is the addition of a generalised draft version of the checklist we use when upgrading usegalaxy.be, so other Galaxy admins could use for inspiration when upgrading their instance. it includes a lot of points from our change management process, which I believe is a NIS2 requirement which makes it quite thorough.
The checklist is in general quite catered to how the Belgian instance is set up, so please add suggestions to make it less instance specific where possible! I'll need some help updating the rest of the tutorial.
I have not deployed this locally so it probably looks wrong.
All feedback and contributions welcome!
TODO:
Update rest of the tutorial's textOut of scope for this contribution.Update tutorial screenshotsOut of scope for this contribution.@pauldg and me are also looking into BioBlend if it could help with the testing of some popular tools and workflows. But this is out of scope for this pull request (testing done manually atm).