On 12/10/2010 02:57 PM, Kevin P. Fleming wrote: > On 12/10/2010 01:45 PM, sean darcy wrote: > >> This was supposedly fixed in 1.6.2 on November 22, 2010. So isn't the >> fix in 1.6.2.15, released 12/8? >> >> In any event, that bug has been declared fixed, so you can't add a note. > > Not necessarily, no. Releases go through a 'release candidate' phase for > a week (or two, sometimes three) before being declared 'ready', so fixes > made before the release date aren't necessarily included. The changelog > included in the release will always indicate what revisions are included > in it, though. > 1.6.2.15-rc1 was released, or at least announced, on November 23. In any event, it'd seem that the purpose of rc's should be to catch regressions like this one.
A minor complaint, from an otherwise very satisfied user, sean -- _____________________________________________________________________ -- 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
