Hey All,
Just wanted to let everyone know (who wasn’t aware yet) that FreePBX 15 is now officially in a released state. Read the release announcement at:
If you encounter any issues, feel free to create a ticket on issues.freepbx.org.
Best wishes to you all, and happy release day!
Matthew Fredrickson
Congratulations to the FreePBX Team!
Thanks so much for the kind response @tm1000! The list would not be complete without recognizing your contributions and the other members of the community that contributed to the release as well. Hope you are doing well, and best wishes!
Matthew Fredrickson
Thanks for catching that @jfinstrom ! I thought we’d already had it pushed out but maybe it hadn’t made it yet. Also, thanks for your contributions as well on the FreePBX 15 release.
Matthew Fredrickson
Are you really releasing FreePBX 15 with all these modules still in EDGE status?:
root@FreePBX:~# fwconsole ma showupgrades
No repos specified, using: [standard,extended] from last GUI settings
Up to date.
root@FreePBX:~# fwconsole ma showupgrades --edge
Edge repository temporarily enabled
No repos specified, using: [standard,extended] from last GUI settings
Upgradable:
+----------------+---------------+----------------+
| Module | Local Version | Online Version |
+----------------+---------------+----------------+
| announcement | 15.0.3.6 | 15.0.3.9 |
| arimanager | 15.0.3.3 | 15.0.3.6 |
| asteriskinfo | 15.0.4.1 | 15.0.5 |
| backup | 15.0.8.61 | 15.0.8.66 |
| blacklist | 15.0.2.6 | 15.0.2.9 |
| calendar | 15.0.4.6 | 15.0.4.16 |
| callback | 15.0.5 | 15.0.7 |
| callforward | 15.0.8 | 15.0.10 |
| callrecording | 15.0.7.8 | 15.0.7.10 |
| callwaiting | 15.0.4.1 | 15.0.4.2 |
| cdr | 15.0.11 | 15.0.15 |
| cel | 15.0.11 | 15.0.15.4 |
| certman | 15.0.10 | 15.0.14 |
| cidlookup | 15.0.7 | 15.0.13 |
| conferences | 15.0.6.5 | 15.0.7.4 |
| contactmanager | 15.0.8.9 | 15.0.8.23 |
| core | 15.0.9.44 | 15.0.9.48 |
| customappsreg | 15.0.11 | 15.0.13 |
| dahdiconfig | 15.0.5.1 | 15.0.5.4 |
| dashboard | 15.0.1.1 | 15.0.3 |
| daynight | 15.0.7 | 15.0.11 |
| dictate | 15.0.4 | 15.0.6 |
| directory | 15.0.12 | 15.0.15 |
| disa | 15.0.4.6 | 15.0.4.7 |
| donotdisturb | 15.0.5 | 15.0.6 |
| fax | 15.0.13 | 15.0.18 |
| filestore | 15.0.3.3 | 15.0.3.4 |
| findmefollow | 15.0.13 | 15.0.16 |
| hotelwakeup | 15.0.5.1 | 15.0.5.4 |
| iaxsettings | 15.0.5 | 15.0.6 |
| ivr | 15.0.14 | 15.0.20 |
| languages | 15.0.6 | 15.0.9 |
| manager | 15.0.5 | 15.0.7 |
| miscapps | 15.0.4 | 15.0.7 |
| miscdests | 15.0.2.5 | 15.0.2.8 |
| music | 15.0.11 | 15.0.16 |
| outroutemsg | 15.0.7 | 15.0.9 |
| paging | 15.0.4.10 | 15.0.4.13 |
| parking | 15.0.9 | 15.0.14 |
| phonebook | 15.0.7 | 15.0.11 |
| pinsets | 15.0.1.6 | 15.0.1.9 |
| pm2 | 15.0.3.6 | 15.0.3.7 |
| presencestate | 15.0.5 | 15.0.7 |
| queueprio | 15.0.5 | 15.0.9 |
| queues | 15.0.9 | 15.0.15 |
| recordings | 15.0.3.4 | 15.0.3.9 |
| ringgroups | 15.0.11 | 15.0.11.4 |
| setcid | 15.0.4 | 15.0.8 |
| sipsettings | 15.0.6.7 | 15.0.6.16 |
| sipstation | 15.0.4.2 | 15.0.5.3 |
| soundlang | 15.0.4.1 | 15.0.5.6 |
| superfecta | 15.0.2.13 | 15.0.2.19 |
| timeconditions | 15.0.12 | 15.0.14 |
| tts | 15.0.8 | 15.0.9 |
| ttsengines | 15.0.4.3 | 15.0.4.6 |
| userman | 15.0.8.2 | 15.0.19 |
| vmblast | 15.0.11 | 15.0.11.3 |
| voicemail | 15.0.17.5 | 15.0.18.8 |
+----------------+---------------+----------------+
Resetting temporarily repository stateI’m fairly sure there are always modules in the edge repositories as development / testing is ongoing. I could be wrong, but it looks like that is what you’re seeing here.
Module updates are published continuously. When an update is first published it goes to the edge repo, and after time and testing then goes to the stable repo. This is true of all supported versions of FreePBX and has zero to do with whether a version is in general release or not.
I would think you’d want to get a product stable before releasing it. The quantity, age, and impact of all these edge updates that aren’t considered stable yet is not a glowing recommendation.
You have a fundamental misunderstanding of what edge means and how it is employed. It’s existence INCREASES reliability of a system. I was sure we had an old blog post describing it in detail, but I can’t find it.
Again, module updates are published continuously throughout the entire supported life of the product. Before any new code is released to all users in the stable repo, it spends some time in the edge repo so it can be tested and so we can do a proper QA.
I seem to recall (and that’s never very reliable) that the rough time in Edge for a module was about two weeks. That no longer seems to be the case.
Can you talk more about the progression from edge to stable? What is the QA schedule like, and how long should we expect? Do some modules need more time in edge than others?
https://wiki.freepbx.org/plugins/servlet/mobile#content/view/62359662
Sorry for the mobile link
But how do we upgrade?
The ‘beta’ upgrade tool still has ‘Beta Warnings’. I tried uninstalling the upgrade tool in case there was an updated version lurking in the repos but no luck.
This is too much of a tease to announce that the stable version is finally available… …when it isn’t!
I wanted to add a bit more on top of the blog post above from @jfinstrom back in 2016.
Edge module releases were originally two weeks.
That was back in 2016 before FreePBX had a proper QA team in place.
With the introduction of the full Sangoma QA team the time frame changes drastically for each module and depends on the complexity of the issue therein. Some issues can take a week. Some can take two weeks and others can go on for a while. QA does its testing from edge because that is the closest release to the user base they can get to (encoded and packaged and signed) so it’s the best way to test.
This means that modules can appear to be forever in edge while older releases are pushed out while new features or issues are worked on. In the past modules were just published when the tickets were closed.
This caused users to complain that modules releases were happening too quickly and sometimes with unstable bugs. Since the development cycle of freepbx is ongoing and doesn’t follow the same development cycle as asterisk we decided to have a staging system. Sort of like how chrome has a beta. Canary and nightly (and actually the backend mirror server supports all of these tracks but we only ever implemented edge!)
Since modules are continually worked on I doubt you’d notice very many modules that only say stable with no edge releases. Especially with over six people working on freepbx development full time!
If you have a pbxact system you notice this even less because modules are pinned to specific versions of releases. Even edge modules are pinned.
I believe when 14 went stable we had quite a few modules in Edge as well and even if we didn’t after 5 days we definitely had quite a few.
With a full QA team in place release cycles of Edge modules should probably be re-clarified because the blog post from 2016 and user expectations are a little outdated.
Thats not bad. It’s just progress.
The problem is: FreePBX 15 has major problems unless you install most (all?) of the Edge version modules.
Some non-Edge modules won’t even install (like UCP, which is a prerequisite for others). Backup/Restore is a disaster without installing Edge modules (and problems are still being discovered and fixed as new Edge versions).
Calling FreePBX 15 stable when a large number of its modules (60+) aren’t yet considered stable is not being realistic.
I personally think all v15 edge modules should be cut over to stable now and that be called FreePBX 15 GA. It’s a better situation than current stable. But I don’t work here. 
This is why I’ll be doing the same thing I did with v14. Waiting for at least 6 months before even attempting to start putting it in production. I’ll spin up a v15 box just to see what is happening with it but outside of that I won’t be recommending anyone move to v15 immediately (my customers that is).