NS 7 is EOL, this has been advocated for a long time to prepare users to migrate to NS8. However, the NS updates bot continues to announe updates for NS7. In case of urgent security updates, it is understandable to cover the ‘grace period’ of migrating to NS8. However it seems that app and system updates continue, which is very confusing in case of EOL, e.g.
This is just a recent example. Multiple updates from various apps have seen the light of day since NS7 became EOL. What is the vision and message here pls?
I believe it is Centos 7 in EOL and not Nethserver 7 itself.
Keep in mind that there are hundreds of Nethserver 7 Enterprise installations that can’t be replaced overnight, whether it’s because of the difficulty of doing the migration, whether it’s because some things are still missing, whether it’s because customers don’t hear from us, and a thousand other reasons.
Nethesis is taking it upon itself to keep both the operating system and the apps “bug free.”
I think Saitobenkei’s got an important point. The NS7 release notes also mention the EOL date of CentOS 7, not NS7, because it hasn’t been precisely defined what happened before and after that date from NethServer’s side.
In my opinion, the important difference between before and after CentOS 7’s EOL date is that while we were mostly focused on implementing new features and general solutions to be distributed through RPM updates, now the solutions are evaluated case by case, with a focus on migrating from NS7 to NS8.
For example, if we discover a new bug in the NS7 mail server today, the solution will most likely be provided as a response in the forum, without a corresponding RPM release. If the bug is related to migration, a fix will probably be released. If the bug affects a CentOS package, we will most likely adopt the CentOS community’s solution. These are just possibilities; as I mentioned, everything is evaluated case by case since there are no hard and fast rules.