Originally Posted by Kier

As you will probably have noticed, vBulletin.com has been unavailable on a regular basis in the past few days.

Unfortunately, the tedious DDoS attacker is back in action and is using his army of hapless Win32 zombie machines to flood our connection, resulting in the server being unable to service our customers.

While this is annoying, inconvenient and tedious, rest assured that it is not slowing the pace of development towards the next vBulletin 3 release.

Originally Posted by Kier

Those of you who have been watching the bug tracker over the past few days will have noticed that the number of unresolved bugs has been gradually creeping down as we have been working to fix the last remaining (known) problems with vBulletin 3.

As I type this, the bug tracker shows 0 unconfirmed issues, 4 confirmed issues and 36 issues awaiting feedback from users. It is those issues awaiting feedback that now need attention, but to do that we need your help. If you have ever submitted a bug report, or if you just feel like helping out, please have a look through the list of bugs awaiting feedback and if you can make a helpful contribution, please post, especially if you are the person from whom we are awaiting feedback!

Based upon the rate at which Mike, Freddie, Scott and I are currently dispatching bugs, we believe that we will be ready to put vBulletin 3 Release Candidate 1 in the Members' Area at some point on Monday (January 5th). Release Candidate 1 will not contain the final vBulletin 3 images, as they are still in development and will appear in a forthcoming release with or before the final 3.0.0 version.

Now back to work...