xchat-gnome 0.26.2 has been tagged, though it hasn’t yet been uploaded to ftp.gnome.org. Instead, I am pushing for an immediate 0.26.3 release—hopefully the final release in the GTK+ 2.x series—followed by xchat-gnome 0.3.0 targeting GNOME 3.
Apologies for the delay in releasing a new version. I recently relocated to Pune and am searching for accommodation, after which I’ll be setting up broadband internet. Once that is sorted out, I will resume active work on xchat-gnome. In the meantime, patches and contributions are very welcome! P.S.: xchat-gnome now has an official mailing list.
I am currently one of the maintainers of xchat-gnome and am working steadily toward releasing version 0.26.2. Track progress on GNOME Bug 602311.
You love chatting over IRC, IRC is life, and you need your IRC client to support fullscreen mode! Look no further: xchat-gnome requires only a trivial patch to support fullscreen. For more information, see Fullscreen support for xchat-gnome (GNOME Bug 445638). Yes, xchat-gnome needs your love!
Upon quitting Totem, I heard a ping. This came from xchat-gnome (via the sound-notification plugin). It turns out gnome_sound_play was being used to play the sound, which defaults to the ESD backend: gnome_sound_play("../../data/message.wav"); ESD has been superseded by PulseAudio in most major distributions. I would prefer moving to a GStreamer-based backend, so I rewrote the code to use GStreamer. However, the ping still didn’t work while I was playing music through Totem. ...
Ticking “Away” worked like a charm on xchat-gnome, but unticking it didn’t do any magic. This turned out to be a bug fixed upstream (GNOME #462031). Grepping the code revealed a rather trivial fix, which on further lookup was part of the Fedora 9 build. I ended up filing a bug report (Fedora #430883). A package was released with the stated fix, which crashed xchat-gnome whenever one tried to set or unset away: ...