Skip to content

Conversation

@B0r1sD
Copy link
Contributor

@B0r1sD B0r1sD commented Mar 12, 2025

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:

  • Build GTN locally
    • See if checkboxes work
  • Update rest of the tutorial's text
  • Update tutorial screenshots
  • Discuss checklist with Galaxy (instance) admins
  • Add myself as contributor
  • ...

@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).

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.
@github-actions github-actions bot added the admin label Mar 12, 2025
* 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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe just pont to https://docs.galaxyproject.org/en/master/project/releases.html .. this way the info in GTN can not go outdated.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah that was my initial idea, thought copying it over would ensure more people read it. It is an easy change then.

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe a very short summary here

@B0r1sD
Copy link
Contributor Author

B0r1sD commented Aug 14, 2025

To be completed after we've upgraded to v25.0 and put the upgrade checklist in practice on more time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants