|08 Apr 2009||#11|
| || |
An "escrow" build means code development is ceased as developers and beta testers hunt for recall class bugs. The escrow code is considered the release to manufacturing code.
"would M$ actually hand over their source code to a third party? i think NOT !!
imagine if Windows source code is leaked and we can all emulate Windows fully on Linux LOL"
Well, they do, on a regular basis, with the pre release of any RC. It is one of the only ways that hardware, and some software, companies could possibly know how to write new code, should there be large changes in the code structure.
This is Microsofts own definition:
"You must be able to recompile the released application at any time after its release. This requires that you maintain the ability to recreate the application build environment"
It is a term being a little misused by the outside world, if Microsoft are staying on schedule. They are not planning an RC2, so the RC1 would, in fact, be the "Escrow"
|My System Specs|
|Similar help and support threads for2: RC-Escrow?|
|Windows 7 SP1 Build 7601.16556 Beta 1 Escrow Leaked....||News|
|Office 2010 RTM Escrow Build 14.0.4734.1000 Leaked||News|
|RC (escrow?) milestone reached!||General Discussion|
|Windows 7 RTM Escrow!!!||General Discussion|
|Win7 RTM Escrow Leak after June 19, 2009||General Discussion|
|Testers get RTM-Escrow build of SP2 for Vista, Server 2008||News|
|Testers get RC-Escrow build of SP2 for Vista and Server 2008||News|