NethServer 6.7 roadmap

(Davide Principi) #1

I also say the 6.7 Beta ISO would start with the actual 6.6 feature set. Allowed changes in the Final version:

  • default values changes
  • changes to UI appearance, behavior
  • new (documented) features, compatible with existing ones

After 6.7 Final is released, it becomes the new “rolling release” and 6.6 will not receive any update.

If I remember correctly these are the same rules applied to the 6.6 release.

Please comment!

NethServer 6.7 Beta1 ready for testing
(Alessio Fattorini) #2

That’s great, can we gather a few 6.7 goals?

Template/role base setup wizard after the installer wizard
(Davide Principi) #3

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.

Change of NethServer upgrade policy
(Davide Principi) #5

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:

(Davide Principi) #6

Is it the only goal for 6.7 release? No other proposals?

Shall we set a proposal deadline to move forward?

(Alessio Fattorini) #7

I moved 4 posts to a new topic: No WebServer in my Software Center

(Giacomo Sanchietti) #8

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.

(Alessio Fattorini) #9

What are you meaning with these two points?

(Davide Principi) #10

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.

What are we looking at in upgrading to 6.7?
How can we celebrate 6.7 release?
(Alessio Fattorini) #11

That’s a nice upgrade already released only for 6.7:
Upgrade roundcubemail

(Jonathan Dumont) #12

so 6.7 is released tomorrow ?

(Alessio Fattorini) #13

Don’t think so, hope for the end of the September!

(Jonathan Dumont) #14

it is possible to upgrade Apache, PHP and SSL to be more compliant ?

(Alessio Fattorini) #15

Compliant with?
These are the versions for such software on Centos 6.7 and obviously on NethServer 6.7:

(Alessio Fattorini) #17

I moved a post to a new topic: Missed the package for WebTop4 on 6.7

(Davide Principi) #18

I moved 3 posts to a new topic: What do you mean with “rolling release”?

(Davide Principi) #19

:checkered_flag: 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!