Which way do you prefer for the upgrade to 6.7?

It recalls what I’ve done for my NS Enterprise customers for the upgrade from 6.5 to 6.6. That time there were some things to fix, today it is straightforward thus I think it is not required.

Hi Davide,

Ok.
It’s clear for me that the upgrade to 6.7 must be done in two steps as you said.
Also, it’s not a big effort to do this from CLI, even for me! :smile:

So, which Scenario?

Maybe for the next upgrade will be possible to do this (One Click Upgrade Button) from time. :pray:
I will add this to My wishes list. :wink:

3 Likes

Ok, let’s go with the simplest path:
the nethserver-release-6.7 rpm will be released inside the nethserver-updates repository for 6.6.

Update procedure
From the GUI: users must press the update button to update the 6.6 to latest released packages and install the new nethserver-release RPM. After the yum cache is expired (12 hours), new updates will be available for the real upgrade to 6.7.

For the next releases, we have to figure out a new way (outside yum) to push the release upgrades.

2 Likes

Is it worth adding this as alternative upgrade procedure to release notes?

It has already been written down :wink:

http://docs.nethserver.org/en/latest/release_notes.html#manual-upgrade-from-6-6

I’m sorry, I see only the Manuale Upgrade section we have since RC1… What happens?

Edit:

The system can be upgraded from the command line.

Of course, it can be upgraded from the Software Center too :wink:

With this awesome new way to upgrade…

I wil expect the same way to upgrade from 6.7 to 7.1 :stuck_out_tongue_winking_eye: