Build lab

A lab or a VBL (virtual build lab) commonly refers to a team working on a part of the Windows operating system, or the source code branch that the team works on. Originally, a build lab was a room with machines periodically producing official builds of Windows NT. Initially, there was a single build lab for the entire project, however, as the number of developers grew, teams working on different parts of the operating system were assigned their own virtual build labs, which included a branch of the project code, as well as the infrastructure to build the code. This carried over to Source Depot branch names, which led to the term being also used for the teams themselves and the branches. The branch name forms a part of the build tag, a unique identifier of a Windows compile.

Builds that were not built by the build lab machines, but are rather compiled by individual Microsoft employees, are called private builds. They are identified by having the VS_FF_PRIVATEBUILD file flag set in the executable's version information and by including the account name of the individual or service that initiated the build in the branch part of the build tag.[a][b]

Labs[edit | edit source]

Microsoft has used several branching systems since the start of Windows XP development, which differ in the hierarchy of labs as well as in the naming scheme. However, there are some specifics common to most schemes, such as the presence of a top-most main branch, or the use of special branches for important development milestones.

Whistler and pre-reset Longhorn[edit | edit source]

The top-most branch (sometimes called the "trunk") was called main, which integrated changes from all labs. Under it were several numbered labs, each of which was working on a separate part of Windows, such as:[c]

  • Lab01: Kernel
  • Lab02: Networking
  • Lab03: Server[d]
  • Lab04: Terminal Services[1]
  • Lab06: User interface
  • Lab07: Internet Information Services/COM+

These labs also had a "_N" branch, which served as a buffer between main and the actual branch. For example, changes from main would first get integrated into Lab06_N before later being integrated into Lab06 in a process called forward integration. The same applied for reverse integration, where the lab would first integrate changes into its N-branch before integrating them into main.

There were also idx (internal development workstation/server) branches, builds from which are usually recompilations intended for TAP/OEM partners. However, they were also occasionally released for public testing, e.g. Windows Longhorn build 4074 or Windows XP build 2257.

Before the release of Windows XP, the trunk was forked into the xpclient branch while the main branch moved on to track Windows Server 2003 development. After the final version was shipped, new branches were created for updates, hotfixes and Service Pack development. Similarly, the dnsrv branch[e] was forked from the trunk before the release of Windows Server 2003.

Since Longhorn reset[edit | edit source]

The lab hierarchy was overhauled after the development reset of Longhorn to address the flaws that plagued most of the pre-reset period. Instead of having a small amount of general virtual build labs each focusing on a different general scope of Windows functionality, a new hierarchial model with considerably more feature branches was introduced, which helped reduce the amount of code to reverse integrate for branch. Microsoft also set stricter criteria for reverse integrating changes from the labs into the trunk, which was now renamed to winmain.

The trunk branch was later renamed to rsmain at some point after the release of Windows 10, and then to rsmaster after the Windows source repository's conversion to Git, likely to comply with the Git convention of calling the top-most branch the master branch. At some point after February 2021,[2] the branch was renamed back to main. This was likely done in order to follow suit with other Microsoft projects[3] after the master/slave terminology became a subject of controversy in 2020 due to alleged slavery connotations.[4]

Feature branch prefix[edit | edit source]

Microsoft has used multiple prefixes to refer to feature branches over time:

Windows 10 November Update and Windows 10 Anniversary Update used their respective release branch prefix for feature branches - th2 and rs1, respectively.

Release branch prefix[edit | edit source]

Similarly to the previous system, the main branch is forked off before release to contain update development. The following is the list of known prefixes:

Branch prefixes used by other teams[edit | edit source]

Some teams that use the Windows codebase but are formally separate from Windows releases also use their own branch prefixes:

See also[edit | edit source]

Notes[edit | edit source]

  1. ↑ For example, build 6.0.4067.private/lddm_dev_tech(davidmo).040212-1646 is a private build initiated by the davidmo user.
  2. ↑ Some builds such as 6.0.4002.Lab06_N(ntvbl06).030108-1926 and 6.1.6469.fbl_find_dev(wexbuild).071002-1531 are compiled as private builds but were built by an official build lab machine account.
  3. ↑ Originally, the ntvbl prefix was used for labs, although it was later changed to Lab in the beginning of the development of Windows XP.
  4. ↑ This lab still compiled client builds even though it worked on server components as the build process does not distinguish between client and server SKUs.
  5. ↑ Short for Windows .NET Server
  6. ↑ fs branches were used in parallel with rs branches.

References[edit | edit source]

  1. ↑ Chen, Raymond. The importance of having a review panel of twelve-year-old boys, episode 2, The Old New Thing. 11 April 2013.
  2. ↑ Windows 10 build 21298 (rsmaster)
  3. ↑ Brown, Shelby. Microsoft's GitHub is removing coding terms like "master" and "slave", CNET. 27 July 2020.
  4. ↑ Regarding Git and Branch Naming, Software Freedom Conservancy. 23 June 2020.

External links[edit | edit source]

Retrieved from "https://betawiki.net/index.php?title=Build_lab&oldid=289423"