As you may have noticed, we are making headway on issues that have been affecting our services for quite some time. Our engineers have been working long and hard to repair the many things you've pointed out.

Many of you have asked for a more detailed explanation of what's been going on with VersionTracker. In a nutshell, we've been working to combine two catalogs containing hundreds of thousands of products, and all the information that goes with them. The result of this work is the most extensive software catalog on the planet.

What a week!

First of all, I want to thank all of you for your patience and tolerance as we've continued to work on site maintenance. I realize that this has not been the easiest of transitions, and I truly appreciate the feedback we've received throughout the process.

I also want to reassure you that we're doing everything we can to address all problems in a timely manner. We're working on a variety of issues simultaneously to deliver fixes as soon as they are ready.

For several months, VersionTracker has been hard at work improving our software listings and architecture to provide a more extensive catalog. In August we told you about the new architecture we moved to that allows us to more easily make improvements to the site. Now we're going to perform a major update that will greatly increase our software listings.

Due to the size and nature of the update, the full process is going to take several days to complete. We are working hard, and our goal is for you to receive the same great service you have come to expect from VersionTracker without interruption.

As of this writing on August 27, we are about 80% through the process of implementing a brand new architecture for the VersionTracker database that will allow us to more easily make improvements to the site. This project has taken months of planning and tight collaboration between the VersionTracker engineering team and our counterparts at CNET.

The last step of the process involves moving the data into the new framework, and during this time we have to pause our regular update flow. More on the features of the new architecture later (aimed primarily at developers), but for now we apologize for the lack of fresh updates on the site while we fire up the new engines.