Hi,
8 upgrades since 07/03/25…
(7.7.1→7.9.1)
Don’t you think that’s a little to often?
Greetings
Hermann
If you check their release policy you’ll find they follow the (annoying as hell) “agile” release schedule of a main release once per month around the 1st.
7.7 → 7.8 → 7.9 etc
In the meantime they release important fixes as required - often security ones.
A LTS version has been promised but never materialised.
However, each version is supported for 6 months so you could just upgrade 6 monthly.
But is it then possible to upgrade to the most recent version or do i have to go through the upgradepath…?
According to Rocket you can upgrade directly. See Gazzos comments here:
However, I have always taken a more conservative path - partly for my own sanity, and partly because Q& A has been flaky as hell for years…… I don’t think they test every single upgrade path. It would be horrendously complex.
So I advise others to use the most cautious approach - If I told you to jump 6 releases and it broke you would be hounding me!
I know for certain that some releases have bigger changes than others - I think 7.5 → 7.6 had some which has made back-porting some changes very difficult. That should server as a warning about the difficulties of upgrading.
So my preferred method is
- Read the changelogs
- Read the bugs/issues
- Backup
- Upgrade a version
- Run a few tests and check logs, especially if you have APIs or custom code
- Rinse & repeat
If you use something like docker it is pretty fast. Personally I trail one release behind - so I am currently on 7.8.x as they have released 7.9
I would NEVER upgrade to a x.x.0 release - see 7.9 - already they have released 7.9.1
I have one server that started around 0.24 and another around 0.3x IIRC and they have been upgraded to date with hardly an issue using this method.
So that is the cautious approach.
You can try a direct upgrade over several versions, but YMMV….. 
I’d spend a LOT of time reading changelogs….