Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 29 and Version 30 of ChangeLog


Ignore:
Timestamp:
May 20, 2009, 5:06:36 PM (15 years ago)
Author:
John Bailey
Comment:

2.5.6 was released yesterday.

Legend:

Unmodified
Added
Removed
Modified
  • ChangeLog

    v29 v30  
    11= !ChangeLog: Pidgin and Finch - The Pimpin' Penguin IM Clients That're Good For The Soul! =
     2
     3== Version 2.5.6 (05/19/2009) ==
     4[http://developer.pidgin.im/query?status=closed&milestone=2.5.6 View all closed tickets for this release.]
     5
     6  * '''libpurple'''
     7    * Improve sleep behavior by aggregation of longer timeouts on second boundaries to allow better power saving.  (Arunan Balasubramaniam)
     8    * Fix various crashes on exit.
     9    * Make XML parsing more resilient to interactions with other libraries. This, along with the fix for libxml2 bug 564217, fixes the crashes on connect in XMPP with recent gst-plugins-bad (see #8830 for details).
     10    * Many security related fixes
     11
     12  * '''IRC'''
     13    * Correctly handle WHOIS for users who are joined to a large number of channels.
     14    * Notify the user if a /nick command fails, rather than trying fallback nicks.
     15
     16  * '''MSN'''
     17    * Fix a race condition causing occasional Pidgin crashes.
     18    * Fix some errors about the friendly name changing too fast caused by MSN/Yahoo integration buddies.
     19
     20  * '''XMPP'''
     21    * Less likely to pop up a new conversation window in disregard of the "Hide new IM conversations" preference.
     22
     23  * '''Yahoo'''
     24    * Fix a crash when sending very long messages.
     25    * Fix a bug where UTF-8 status messages get garbled when going idle.
    226
    327== Version 2.5.5 (03/01/2009) ==
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!