Windows 7 nezvanične verzije: Build 7032, 7048...

Officially, Microsoft has always said "three years after the general availability of Windows Vista," which was released on January 30, 2007, and that the release date was also dependent on quality. As with any product in beta, enthusiasts have been making predictions all over the place, most in the timeframe of late 2009 to early 2010. Microsoft employees have been making their own predictions, but the average of their guesses is much earlier in 2009: October 3.

I asked Michael Bohlin, product, here are some dates more or less nailed.
*February 26, TechNet and TrueSec med with Microsoft Windows 7 Summit. Microsoft Windows 7 Summit.
*17-18 March, Tech Days in Västerås, our largest Windows 7 event in the spring.
*May 31 Microsoft itself installed.
*Early in April, after CeBIT, the RC.
*June, July, August, Summer Koll with many presentations.
*RTM and launch company as it stands right now Q3 2009. The cut of all internal guesses here at the office right now is October 3 at 11.10.
*February 2010 the board of trade.

The above quote is a translated version (à la Google) of a Microsoft Sweden partner blog post that Neowin found. It should also be noted that the timeline points to an RC being released in April.

Leaked information from testers now reveals that Windows 7 Build 7048 carries the Release Candidate 1 (RC1) label.

Various sources, especially enthusiasts on Windows-centric forums, indicate that a select pool of Microsoft testers have received Windows 7 Build 6.1.7048.winmain_win7rc1.090211-1625. Microsoft has yet to confirm or deny that, as at just a little over one month since the public launch of Windows 7 Beta it has started compiling builds of the operating system belonging to the RC branch.
However, the version label associated with Windows 7 Build 7048 indeed suggests that the Redmond company has branched off winmain. At the same time, “090211-1625” indicates that Windows 7 Build 7048 was compiled on February 11, 2009, at 4:25 PM.

Nevertheless, the leaked details on Windows 7 Build 7048 RC have to be taken with a grain of salt, as Microsoft has yet to unveil the actual naming scheme that will be associated with RC branch builds. Before Windows 7 Build 7048, testers leaked information and screenshots on Windows 7 Build 7032 (6.1.7032.0.winmain.090129-1812).

But, for the time being, only the bits for Windows 7 Build 7022 are available for download in the wild, with the 32-bit flavor having been leaked to BitTorrent trackers. As far as Microsoft is concerned, mum's the word for the Windows 7 Release Candidate, which is reportedly planned for an April 2009 launch.

Test Updates for Windows 7 Beta Users
petak, 20. februar 2009, 05:23:19 | Brandon LeBlanc
Starting February 24, we will be releasing up to 5 test updates to PCs running the Windows 7 Beta (Build 7000) via Windows Update. These updates allow us to test and verify our ability to deliver and manage the updating of Windows 7. We typically verify servicing scenarios during a beta.

Windows 7 Beta users will be notified that new updates are available beginning February 24 through Windows Update. Even if the user has Windows Update configured for automatic update – these test updates will not install automatically. Users will need to manually install the test updates through Windows Update.

These updates do not deliver new features or bug fixes. The test updates simply replace system files with the same version of the file currently on the system.

If all goes according to plan, the Windows 7 Release Candidate build will be released to the public on April 10, 2009.

After rumors sprang up across the blogosphere of a Windows 7 build 7048, we debunked them and along with all the other Windows 7 users, we looked hungrily for information on new builds. Microsoft is currently compiling pre-RC builds of Windows 7, the latest build being 7046. Many beta testers are frustrated that they have not received a build since build 7000, which was released to everyone on January 9, 2009. Unfortunately, Ars has learned that this trend will continue. When I asked Steven Sinofsky, senior vice president for the Windows and Windows Live Engineering Group, if Microsoft Connect testers as well as MSDN and TechNet subscribers will get the RC before the public, Sinofsky told me no: "The build will be available broadly."

When will this occur? Well, sources are continuously pointing to a release of the RC build in April, and now that timeframe has been further narrowed down. According to Neowin, "the official release date is set for April 10, 2009." Whether the Windows development team will be able to meet this date is another story entirely, but development is going quite well I'm told, so as of right now, I'm optimistic that the release date will be met.

Sinofsky has also been talking to Geeksmack, sending them an e-mail yesterday dispelling the buzz that Microsoft wasn't paying attention to what testers were saying: "We have received an amazing amount of feedback, many suggestions for new features too, during the beta—over 500,000 suggestions just from the Send Feedback button (which is only one of many feedback mechanisms). Putting that in perspective it is 500 suggestions for each and every developer on the Windows team, just since beta!" That is a lot of feedback to go through, and it looks like Sinofsky is up to the challenge.

calexx:Normalna beta 7000 je radila sasvim ok, ako ne računam drajvere za zvučnu zbog koje sam vrlo retko palio sedmicu.

...
We’ve been quite busy for the past two months or so working through all the feedback we’ve received on Windows 7. It should be no surprise but the Release Candidate for Windows 7 will have quite a few changes, many under the hood so to speak but also many visible. Some have asked if the featureset is "frozen" then what will we change--we change a lot of things in the beta based on feedback and we try to do so in a systematic manner with the focus on the goals for the release. The goal of having a fully functional Beta was to make sure we received reliable feedback and not a lot of "hey this doesn't work at all" sorts of reports. This has allowed us to really focus on delivering a refined RC where the changes we made are all the reflection of feedback we have received.
...