Microsoft Corp. today said it would issue a release candidate (RC) for Internet Explorer 8 in the first three months of 2009, indicating it will ship its newest browser sometime in the first half of the year.

"We will release one more public update of IE8 in the first quarter of 2009, and then follow that up with the final release," Dean Hachamovitch, the general manager overseeing IE8, said in an entry to a company blog.

The current version is Beta 2, which was released in late August.

If Microsoft's past performance is an indicator, the final of IE should launch in the first half of 2009. Its last major update, IE7, hit release candidate status in late August 2006, and shipped as a final version in mid-October of that year, a span of just under two months. Even if Microsoft pushes the release candidate of IE8 to users in March 2009, it should still be able to manage to ship a final edition by the end of June.

Hachamovitch said the IE8 release candidate would be the final, more or less. "We want the technical community of people and organizations interested in Web browsers to take this [release candidate] update as a strong signal that IE8 is effectively complete and done. They should expect the final product to behave as this update does." He went on to urge Web site and Web services developers to test their work against the release candidate when it ships.

As other Microsoft officials have done since IE8 first appeared, Hachamovitch declined to set a specific date, however. "Our plan is to deliver the final product after listening for feedback about critical issues," he said. Previously, all that the company would commit to was a release prior to the launch of Windows 7, which in turn has been pegged for late 2009 or even early 2010.

Although several people who left comments on Hachomovitch's blog applauded the disclosure of the rough timeline, others thought Microsoft is moving too fast.

"'We listen,' 'We are listening,' 'We've heard you,' and other stupid marketing sentences...you've just heard nobody," said a user identified only as Oliver. "Where's beta3? Beta2 was unusable and crashed all the time, so we can't test it. Please give us a testable beta before a release candidate."

"This has been said many times before, so I'll make it simple," added someone identified as Jason Ashdown in another comment to the post. "We want a Beta 3! Beta 2 was nowhere near the quality we expected. Before getting to a [Release Candidate], we want to get the last set of bug reports before you get to RC1. Closing the door now would be a horrible mistake."