Windows 7: Betas

The Windows 7 Beta is out.

Get it here

The current pre-Beta version of Windows 7 is 6801,   6956, 7000, 7025, 7264.

From Softpedia:

"Forget Windows 7 Beta Build 7000, Microsoft has already moved past what Steven Sinofsky, senior vice president, Windows and Windows Live Engineering Group, referred to as the four core development milestones of the next iteration of the Windows client (M1, M2, M3 and Beta). In this context, the Redmond company has already debuted the testing of post-Beta builds for Windows 7.

The leaked screenshots and version information available for Windows 7 post-Beta Build 7025 are illustrative examples of Win 7's evolution. At this point in time, Windows 7 Build 6.1.7025.0.090120-1850 is live and already deployed in testing environments.

Fact is that, even at the end of 2008, before Win 7 Beta was offered to a select pool of testers and subsequently leaked, Scott Wylie, Microsoft's New Zealand director of Development and Platform Strategy, revealed that Microsoft went past the 7000 mark with the platform's development process.

Ahead of Christmas, Wylie leaked a screenshot of Windows 7 Build 7004, which he referred to as pre-Beta, an inaccurate statement, given that the version number superseded that of the official Beta, namely 7000.

And since the Beta of Windows 7 is actually Build 7000, this means that all later builds labeled with higher version numbers are post-Beta, and belong to the the Release Candidate branch of the operating system, including Build 7025 (screenshots via PCBeta). 7025 is at least pre-RC, but signaling that Microsoft is moving Windows 7 toward Release Candidate, even though the default wallpaper continues to be the Beta Fish."

But what is a Beta or a pre-Beta? Especially a Windows 7 Beta or pre-Beta?.

A software release is the distribution (whether public or private) of an initial or upgraded version of a computer software product. Each time a software program or system is changed, the software engineers and company doing the work decide on how to distribute the program or system, or changes to that program or system. Software patches are one method of distributing the changes, as are downloads and compact discs.
Software release stages

The software release life cycle is composed of different stages that describe the stability of a piece of software and the amount of development it requires before final release. Each major version of a product usually goes through a stage when new features are added, or the alpha stage; a stage when it is being actively debugged, or the beta stage; and finally a stage when all important bugs have been removed, or the stable stage.

Intermediate stages may also be recognized. The stages may be formally announced and regulated by the project's developers, but sometimes the terms are used informally to describe the state of a product. Conventionally, code names are often used by many companies for versions prior to the release of the product, though the actual product and features are rarely secret.

Pre-alpha: initial development stage

Pre-alpha stage consists of the period of time from the start of the development phase until Alpha release, (or any other stage that comes next, in case developers opt to have no Alpha release). Sometimes a build known as pre-alpha is issued before the release of an alpha or beta, as developers need to see how features work in action as the development process proceeds.

In contrast to alpha and beta versions, the pre-alpha is not feature complete. When it is used, it refers to all activities performed during the software project prior to software testing. These activities can include requirements analysis, software design, software development and unit testing.

In typical open source development, there are several types of pre-alpha versions. milestone versions include specific sets of functions and are released as soon as the functionality is complete.

Nightly builds are versions that are usually automatically checked out from the revision control system and built, typically over night; these versions allow the testers to test the recently implemented functionality immediately, and find the new bugs.

Alpha: internal test

The alpha build of the software is the build delivered to the internal software testers, that is, persons different from the software engineers, but usually internal to the organization or community that develops the software. In a rush to market, more and more companies are engaging external customers or value-chain partners in their alpha testing phase. This allows more extensive usability testing during the alpha phase.

In the first phase of testing, developers generally test the software using white box techniques. Additional validation is then performed using black box or grey box techniques, by another dedicated testing team, sometimes concurrently. Moving to black box testing inside the organization is known as alpha release.

Beta: public test

'Betaware' is a nickname for software which has passed the alpha testing stage of development and has been released to a limited number of users for software testing before its official release. Beta testing allows the software to undergo usability testing with users who provide feedback, so that any malfunctions these users find in the software can be reported to the developers and fixed. Beta software can be unstable and could cause crashes or data loss.

A 'beta version' is the first version released outside the organization or community that develops the software, for the purpose of evaluation or real-world black/grey-box testing. The process of delivering a beta version to the users is called beta release. Beta level software generally includes all features, but may also include known issues and bugs of a less serious variety.

The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software. They receive the software for free or for a reduced price, but act as free testers.

Beta versions test the supportability of the product, the go-to-market messaging (while recruiting Beta customers), the manufacturability of the product, and the overall channel flow or channel reach.

Beta version software is likely to be useful for internal demonstrations and previews to select customers, but unstable and not yet ready for release. Some developers refer to this stage as a preview, a prototype, a technical preview (TP) or as an early access. As the second major stage in the release lifecycle, following the alpha stage, it is named after the Greek letter beta, the second letter in the Greek alphabet.

Often this stage begins when the developers announce a feature freeze on the product, indicating that no more feature requirements will be accepted for this version of the product. Only software issues, or bugs and unimplemented features will be addressed.

Developers release either a closed beta or an open beta; closed beta versions are released to a select group of individuals for a user test, while open betas are to a larger community group, usually the general public. The testers report any bugs that they found and sometimes minor features they would like to see in the final version.

An example of a major public beta test was when Microsoft started releasing regular Windows Vista community technology previews (CTPs) to beta testers in January 2005. The first of these was build 5219. Subsequent CTPs introduced most of the planned features, as well as a number of changes to the user interface, based in large part on feedback from beta testers.

Windows Vista was deemed feature complete with the release of build 5308 CTP, released on February 22, 2006, and much of the remainder of work between that build and the final release of the product focused on stability, performance, application and driver compatibility, and documentation.

When a beta becomes available to the general public it is often widely used by the technologically savvy and those familiar with previous versions as though it were the finished product. Usually developers of freeware or open-source betas release them to the general public while proprietary betas go to a relatively small group of testers.

Recipients of highly proprietary betas may have to sign a non-disclosure agreement. A release is called feature complete when the product team agrees that functional requirements of the system are met and no new features will be put into the release, but significant software bugs may still exist.

Companies with a formal software process will tend to enter the beta period with a list of known bugs that must be fixed to exit the beta period, and some companies make this list available to customers and testers.

As the Internet has allowed for rapid and inexpensive distribution of software, companies have begun to take a more flexible approach to use of the word "beta". Netscape Communications was infamous for releasing alpha level versions of its Netscape web browser to the public and calling them betať releases.

In February 2005, ZDNet published an article about the recent phenomenon of a beta version often staying for years and being used as if it were in production-level. It noted that Gmail and Google News, for example, had been in beta for a long period of time and were not expected to drop the beta status despite the fact that they were widely used; however, Google News did leave beta in January 2006.

This technique may also allow a developer to delay offering full support and/or responsibility for remaining issues. In the context of Web 2.0, people even talk of perpetual betas to signify that some software is meant to stay in beta state. Also, "beta" is sometimes used to indicate something more like a release candidate such as the Halo 3 public beta.

The term beta test comes from an IBM hardware product test convention, dating back to punched card tabulating and sorting machines. Hardware first went through an alpha test for preliminary functionality and small scale manufacturing feasibility.

Then came a beta test, by people or groups other than the developers, to verify that the hardware correctly performed the functions it was supposed to, and could be manufactured at scales necessary for the market. And finally, a c test to verify safety.

With the advent of programmable computers and the first shareable software programs, IBM used the same terminology for testing software. As other companies began developing software for their own use, and for distribution to others, the terminology stuck” and now is part of our common vocabulary.

Release candidate

The term release candidate refers to a version with potential to be a final product, ready to release unless fatal bugs emerge. In this stage of product stabilization (read QA cycle), all product features have been designed, coded and tested through one or more Alpha cycles with no known showstopper-class bugs.

Microsoft Corporation often uses the term release candidate. The term is also used by Mozilla for their release of Firefox 3 RC1. During the 1990s, Apple Inc. used the term “golden master” for its release candidates, and the final golden master was the general availability release.

Other terms include gamma (and occasionally also delta, and perhaps other Greek letters) for versions that are substantially complete, but still under test, and omega or zenith for final testing of versions that are believed to be bug-free, and may go into production at any time. (gamma, delta, and omega are, respectively, the third, fourth, and last letters of the Greek alphabet.)

Some users disparagingly refer to release candidates and even final “point oh” releases as “gamma test” software, suggesting that the developer has chosen to use its customers to test software that is not truly ready for general release. Often, beta testers, if privately selected, will be billed for using the release candidate as though it were a finished product.

A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There may still be source code changes to fix defects. There may still be changes to documentation and data files, and to the code for test cases or utilities. New code may be added in a future release.

RTM

The term “release to manufacturing” or “release to marketing” (both abbreviated RTM) is used to indicate that the software has met a defined quality level and is ready for mass distribution either by electronic means or by physical media. The term does NOT define the delivery mechanism, it only states that the quality is sufficient for mass distribution. The deliverable from the engineering organization is usually in the form of a gold master CD used for duplication or to produce the image for the web.

In most if not all cases, RTM happens prior to general availability (GA) where the product is released to the public.

GA

General availability (GA) is the point where all necessary commercialization activities have been completed and the software has been made available to the general market either via the web or physical media.

Commercialization activities could include but are not limited to the availability of media world wide via dispersed distribution centers, marketing collateral is completed and available in as many languages as deemed necessary for the target market, etc. The time between RTM and GA can be from a week to months in some cases before a generally available release can be declared because of the time needed to complete all commercialization activities required by GA.

Production or live release

The production, live version is the final version of a particular product. It is typically almost identical to the final release candidate, with only last-minute bugs fixed.

A live release is considered to be very stable and relatively bug-free with a quality suitable for wide distribution and use by end users. In commercial software releases, this version may also be signed (used to allow end-users to verify that code has not been modified since the release).

The expression that a software product "has gone live" means that the code has been completed and is ready for distribution.

Other terms for the live version include: live master, live release, or live build. In some areas of software development the live release is referred to as a gold release; this seems to be confined mainly to game software.

Source: Wikipedia.