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.
| * Each version also has an official branch in the GitHub repo named `release_YY.MM`. e.g. *release_21.01* | ||
| The latest updates on the Galaxy release proces can be found here: https://docs.galaxyproject.org/en/master/project/releases.html | ||
|
|
||
| - Long Term Support (LTS) releases happen annually, in the first quarter. |
Contributor
There was a problem hiding this comment.
Maybe just pont to https://docs.galaxyproject.org/en/master/project/releases.html .. this way the info in GTN can not go outdated.
Contributor
Author
There was a problem hiding this comment.
Ah that was my initial idea, thought copying it over would ensure more people read it. It is an easy change then.
Contributor
There was a problem hiding this comment.
Maybe a very short summary here
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
| > - [ ] Bring Your Own Storage connection | ||
| > | ||
| ### Production Upgrade | ||
| If the Tests on the test instance were successful, initiate poduction upgrade process. |
Member
There was a problem hiding this comment.
Suggested change
| If the Tests on the test instance were successful, initiate poduction upgrade process. | |
| If the Tests on the test instance were successful, initiate production upgrade process. |
| Congratulations, you're Galaxy server should now be updated to the latest version. You can check this by going to the Admin UI page or by using the API as described above. | ||
| Congratulations, your Galaxy server should now be updated to the latest version. You can check this by going to the Admin UI page or by using the API as described above. | ||
| > <hands-on-title>Upgrade checklist</hands-on-title> |
Member
There was a problem hiding this comment.
Shouldn't this all section be moved before the upgrade instructions?
| > - [ ] Merge notice banner at least one week in advance | ||
| > - [ ] Make a draft pull request for a news item, which includes emphasis on reporting unexpected behavior, and any new features or changes | ||
| > - [ ] See if the GDPR compliance / data policy page requires updating after the new changes | ||
| > - [ ] Roll back if significant issues arise, following the regression steps |
Member
There was a problem hiding this comment.
Should this line be moved to Post-upgrade ?
| > - [ ] Exporting data | ||
| > - [ ] Exporting workflow runs | ||
| > - [ ] Making a new history | ||
| > - [ ] Removing data |
Member
There was a problem hiding this comment.
Suggested change
| > - [ ] Removing data | |
| > - [ ] Deleting and purging datasets |
| > - [ ] Exporting workflow runs | ||
| > - [ ] Making a new history | ||
| > - [ ] Removing data | ||
| > - [ ] Removing histories |
Member
There was a problem hiding this comment.
Suggested change
| > - [ ] Removing histories | |
| > - [ ] Deleting and purging histories |
| > - [ ] Making a new history | ||
| > - [ ] Removing data | ||
| > - [ ] Removing histories | ||
| > - [ ] Pulsar |
Member
There was a problem hiding this comment.
Suggested change
| > - [ ] Pulsar | |
| > - [ ] Running a job via Pulsar (if configured) |
Comment on lines
+305
to
+306
| > - [ ] Make a pull request to add a notice banner via notices.yml in the relevant repository | ||
| > - [ ] Merge notice banner at least one week in advance |
Member
There was a problem hiding this comment.
I suppose these are specific to your setup?
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:
@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).