In regards to the upgrade plan: recently my commit was merged into master, and it allows building the 1.7 debs on wheezy. Although this combination is officially unsupported, it could be useful for an upgrade path. On 14 Oct 2015 18:56, "Michael Jerris" <mike@jerris.com> wrote:
I will have to make that call once I see what the effect of any of them actually is, and how invasive the fixes are. That being said, now that we have 1.6 releases out there, over time what gets back-ported into 1.4 will be less and less ( I think there was only 1 or 2 patches that went in to 1.4 last week). For anyone holding off on 1.6, it is already time you should be testing this in your labs and figuring out an upgrade plan. There are some significant advances in 1.6 that are not in 1.4 due to architectural restrictions. We need to identify and eliminate any blockers for people to update.
On Oct 14, 2015, at 12:35 PM, Dmitry Lysenko <dvl36.ripe.nick@gmail.com> wrote:
Do you plan to fix these bugs in 1.4 branch?
2015-10-14 0:55 GMT+03:00 Michael Jerris <mike@jerris.com>:
Yes, they notified us a few days ago about it, and we are talking to them about getting access to the software so we can see how well it can help us. Good news at least is it doesn't appear to have found any security issues, but it did find a number of typos, mostly in error cases that are not hit very often. We will be fixing these issues shortly once we have access to the full report so we can review it all properly. As it happens, we do have ongoing work with a number of similar scanners that we use to help improve overall code quality. These tools all seem to have different strengths and weaknesses when it comes to what they can find and what their false positive rate is. This tool is somewhat interesting in that it is the only windows based tool we have had scan this code other than the built in microsoft code analysis functions, so it appears to have found a number of small windows specific issues we have not seen from other tools.
On Oct 13, 2015, at 5:15 PM, Igor Olhovskiy <igorolhovskiy@gmail.com> wrote:
Hi!
I don't know, if developers and maintainers noticed this: http://www.viva64.com/en/b/0351/ Might be helpful )
-- Best regards, Igor
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org