Here is an update on the progress that we made with the next major release, ISPConfig 3.2. In the past, ISPConfig development has become slower and slower due to the vast amount of legacy code that we accumulated in the past 10+ years in ISPConfig 3. Therefore, we decided that it's time to make a straight cut and get rid of that ballast and to make ISPConfig more modular. This cut will happen with the 3.2 release. The 3.1 branch will become an LTS branch that we plan to support with security fixes and fixes for major bugs when 3.2 is available. Here the changes that happen with 3.2: We will support only the current Linux Distributions: - Debian 8 and newer - Ubuntu 16.04 and newer - CentOS 7 and newer - Fedora, OpenSuSE, and Gentoo were not actively supported for some time, but we leave the code for them in the installer for now. Removal of old technologies: - Drop support for Apache 2.2, so Apache 2.4 or newer is required - Drop PHP Modes: CGI, SuPHP, and HHVM (as HHVM drops PHP support) - Apache 2.2 (Apache 2.4 or Nginx is required as web server now) - Courier (Dovecot is the default IMAP/POP3 daemon for quite some time and we will drop support for Courier in 3.2. Systems that still use courier must be converted to dovecot.) Functions removed from Core, they will be reintroduced as an add-on: - Mailman and Mlmmj Mailinglisten manager - The VM Module (OpenVZ is a deprecated technology) - XMPP - MongoDB New Technologies (already implemented) - rspamd as amavis replacement, amavis support will still be available - acme.sh as additional let's encrypt client - Duplicate code in nginx and apache plugin has been moved to a new library. ToDo / Planned (no complete list, just some key points): - New addon installer to replace the current add-on system (the one under System, not the APS installer in sites module). - Slave server to master connection through https (REST) instead of MySQL connects. The old MySQL connects will still be available. - Install ISPConfig updates from the UI (as an option). - Improve modularity of the UI (requirement to be able to re-add some of the functions that we removed from the core) - New web server mode with apache and nginx installed: in this mode, nginx acts either as web server (like a normal nginx server now) or as proxy for apache. This allows us to have a nginx/apache selector in each website where the user can select the web server mode. While @Croydon has done a whole load of cleaning up the code, I'm working currently to get the 3.1.14 release ready. When 3.1.14 is released, then I will put my focus on the remaining 3.2 tasks. The cleanup is currently done in a private branch, it will get merged into master soon.