Build 115 has been released, addressing another batch of minor bugs and bringing us closer and closer to a final release. We also want to thank all of you who voted for us in the recent Hive Five poll; your support and enthusiasm for Trillian is very important to us. Thank you!

Build 114 has been released to fix a login issue with Twitter and resolve a long-standing issue with ICQ usernames showing up as UINs in certain situations. The recent flurry of builds have been going out only to the “beta” portion of our testing team; those of you still on Build 111 should expect to be updated once we’re comfortable with the state of the new builds.

Thanks for your patience as we fix all of these issues, and please let us know if any further problems exist. Have a great weekend!

Build 113 is now available with new bugfixes and regression bugfixes for those of you who courageously tested Build 112. We are trying to fix as many of the bugs testers have been bringing to our attention as “blockers” and 113 cleans up a few of those too. We will roll 113 out over the next few days.

More fixes for the iPhone and Web versions today – Trillian for iPhone Build 269 and Trillian for Web Build 600. Testers for the web version should be automatically upgraded the next time they login to the service, and iPhone users should use the download link in their invitation email to grab the latest build. We’ve also decided to hold off on distributing Windows Build 112 to the general testing population as it introduced a few regression bugs we’d rather not force on everyone, so we’re working on getting Build 113 out instead. Enjoy the new builds!

iPhone testers: the provision file has been updated in 269! Don’t forget to re-install it by following the original instructions in the README file or the build won’t run!

Build 112 is now available and will be distributed to all customers within the next few days. We fixed a few long-standing bugs in this one (autoconnect not sticking comes to mind) and continue to iron out the rest of the bugs as we prepare for a final release. Starting with Build 112, we’re considering each build a potential release candidate. While there will always be bugs, even in a final release, Trillian Astra is starting to stabilize to the point that we’re comfortable giving it out to a large number of people. Please ensure you report any show-stopping bugs to us in Bugzilla so we can fix them!

Our development cycle after the final release will continue almost unchanged from what you see today. Unlike in the past, you won’t have to “sit” with a particular version of Trillian for long periods of time! We’ll continue to fix bugs in our release branch (4.0) while simultaneously introducing new features in our upcoming beta branch (4.1+), so even if a bug doesn’t get fixed for 4.0 “final” there’s a good chance it will be fixed shortly thereafter. We think, within reason, a speedier and more transparent development process will benefit Trillian as a whole and are looking forward to keeping the updates coming.

Enjoy the build!