Can someone confirm if the bug present in #18951 has been fixed in 1.6 or 1.8 ?
If not, then I am stuck on my current version of 1.4, and will not be able to upgrade to either of those two versions, even for security fixes. Julian On 19 April 2011 15:52, Paul Belanger <[email protected]> wrote: > On 11-04-19 09:28 AM, Kristijan Vrban wrote: >> >> @digium >> >> 1. What happened with the 1.4 patches that still wait on >> issues.asterisk.org? e.g. issue #19108 > >> > Once a branch moves into security mode; no more bug fixes will be applied. > If a security issue affects the 1.4 branch, a new release will be created > containing only that fix. > >> 2. What happened with bugfix patches for 1.4 made by the community. >> Will those be ignored now? >> (e.g. i have one more a memleak fix for 1.4 in preparation, that i can >> publish earliest after 2011-04-21) >> > We'd asked you to retest the issue against a supported branch (Asterisk > 1.8), then triage the issue from there. > > -- > Paul Belanger > Digium, Inc. | Software Developer > twitter: pabelanger | IRC: pabelanger (Freenode) > Check us out at: http://digium.com & http://asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- Follow "Ode To Politics" by HB Tasker at http://twitter.com/HBTasker -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
