I have deleted my previous post to this thread, which had been marked as a solution, because I was prevented from editing, and because I don’t believe it solved the primary question raised in this thread.
Throughout the FreePBX 17 release process while I was part of the team, our communications indicated that we would be following the normal release process, that is that the project usually only supports the two most recent major versions. When a new major version launches, the release two versions behind goes EOL. There are links in this thread to blogs and posts stating this.
There doesn’t seem to be any more recent communications from the project indicating anything to the contrary, so it’s reasonable to expect that prior communications stand; that FreePBX 15 is EOL and has been since the 17 GA release. Given the recent major feature release for 15, there’s enough uncertainty at this point for the project to publish a formal statement indicating officially what the status of 15 is, and if it’s not EOL a timeline to when EOL can be expected.
You should expect a formal statement soon on the status of FreePBX versions as well as updates to the downloads available on freepbx.org
AFAIK this roadmap topic is something discussed and presented at AstriCon and there’s of course a lot more going on recently with the change in underlying targeted Linux distros from CentOS based versions up to FreePBX 16 over to Debian based starting in FreePBX 17. This change in Linux distros alone seems enough to justify extended v15 support, and @dicko pointed out earlier that some are still challenged by v17 upgrades.
At this point it would be irresponsible to claim to continue to support FreePBX 15 software or distro. How could you claim to support it when PHP 5 has been EOL for years and SangomaOS hasn’t seen an update for over a year either? The undercarriage has to be supportable in order for the software on top to be supported.
Note, FreePBX 16 distro is basically in this same situation.