Here’s the skinny on the last two weeks:

- We’ve compiled, for the first time, a build of the new Trillian release and have officially commenced the horrible and painful internal testing process. This means that we’re making a best effort at actually using the new build in lieu of Trillian 3. We are also compiling our own list of all the obvious and show-stopping bugs, and fixing them.

- We are now at “Build 2″, with Build 3 hopefully ready this week.

That is all.

For those of you who threw your hats in the ring for testing, please be advised that there is no formal procedure in place to “accept” or “deny” a tester. If you e-mailed me within a reasonable amount of time after my post, and before my followup post, then consider yourself in. If the build goes out and you do not receive it, but feel that you should have, drop me a note.

We have no dates for when the non-Cerulean testing will start. It will not happen until we are completely satisfied (read: fooled into believing we’ve fixed all the bugs) with the internal builds. We will be keeping you all updated, so check the blog every now and then.

Thanks!

- Scott

… we have our 50 testers. Thanks, everyone!

I am in hardware hell.

We’re busy installing new servers for some upcoming developments, and boy is it a pain in the neck. My hat goes off to all of the network engineers out there who spend their days locked in colocation facilities, trusty DB9 cable in tow.

I realize it’s been a year since we’ve released anything substantial. I apologize for that; we’re working on something somewhat different for us and it’s taking a little bit more time than we anticipated.

I want to thank each and every one of you for standing behind us over the years. There are reasons behind every action we make, including our public silences. And while I am unable to share these reasons in full detail, I want you all to know that we truly appreciate your support and we’re working extremely hard on the next release. We do hope you’ll enjoy it.

Anyhow, I am putting my money where my mouth is – we are working on drafting some information about the new release to share with you. I am also going to need some serious testing, so the first 50 people to e-mail me will be guaranteed a slot in our first-wave internal testing program. Want to see a bug fixed? There’s no better way than participating in testing cycles – you can’t win if you don’t play!

Thanks!