My first goal is receive security updates from 6.7 upstream.
If we release 6.7 Beta immediately everyone can upgrade to it and receive security updates. We just need some tests to be sure that upgrading the base system from 6.6 to 6.7 works.
There should not be changes to services behavior during 6.7 Final development, thus I assume an upgraded production system will be stable enough if we’ll follow the usual “rolling release” process.
I expect biggest changes are applied to the ISO installer and affect only new installations.
During 2015 we saw a lot of CVEs and fixes concerning SSL. It’s time to review the default ciphers for each daemon (httpd, dovecot, slapd…) I opened this enhancement:
I would like also to remove lokkit support in favor of shorewall.
Maybe we can always install shorewall as a core firewall implementation and permit to install the web UI (port forward, dual wan, etc) as a separate rpm.
Absolutely, I would like to set the deadline to the 15 of September.
Default values changes affect only new system/package installations. For instance, if a service was by default accessible from any network we can restrict the new default to be accessible only from trusted networks. The change is visible only on new installations, as the current value is retained on upgraded systems.
changes to UI appearance, behavior is self-explanatory, i think. It refers to existing modules, not new ones.
Thanks to @dz00te for his great QA, all 6.7 issues are currently CLOSED/VERIFIED. As there are no new issues, we can leave the beta stage and proceed with NethServer 6.7 Release Candidate 1!