Review and testing continues

I'm going to be continuing my rather tedious review of every code change and continue testing on all my test beds here. I'm hoping to knock out any user reported errata during this phase of development. RC2 will come soon, then following quickly (hopefully) by RC3 after performance testing is complete. At that point, if no major errata exists, version 4 will be released.

As of right now, I know there are a couple user reported problems that have yet to be addressed. I've fumbled around and stalled on them, waiting for the completion of my own review. I find that carefully reviewed code is often the best method of avoiding errata to start with. It is very similar to proof-reading. Sadly, as with proof-reading, it is difficult to do on your own code -- at least not right away (when you look again later after a break, problems then tend to be more visible).

Besides all this product work, our server-side activation system is getting a bit of a boost too. It is being relocated to a more geographically centered server. This offers better access time and performance during high loads, and it will isolate that server. This will be our third web and third database server needed to keep Bitsum Technologies safely afloat. I say safely afloat because the isolation of each server to its specific task is largely to improve overall security.