RTM

  • Thread starter Thread starter Travis King
  • Start date Start date
T

Travis King

I'm hearing a lot of people on this newsgroup mentioning Vista has gone RTM,
but I haven't seen an official sources yet. So, did Vista actually go RTM
or is there just suspicion that Vista has gone RTM? Thanks.
 
Its speculation. Because at MS some persons are on build 6000, certain
persons assume its RTM. But we should take into account, the Windows Team
usually compiles multiple versions of the same build if they believe it has
potential of being RTM.
 
Why do they do that Andre?.
I thought they would work on eliminating one bug at a time with one build at
a time. Obviously they must be using a different strategy.
Please enlighten us.
 
Andre Da Costa said:
It means they have forked the build to stabalize it. This also
means that they are driving a particular build number to something
of quality to deliver to RTM.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
Click to expand...

Andre,

RTM is not handled as a forked process like the Beta builds. Once the
RTM push is under way post the RC builds, the build is not forked.
The main branch is pushed forward to a build that is effectively
escrowed as the RTM, it then undergoes more rigorous testing and any
changes required are built and applied to produce a new escrow, but
these should be rare at this stage after the huge number of test
cycles and builds released both publicly and to the tech beta program
and also released internally and to other programs and test sources.
Ultimately a build is escrowed and then tested by all subcomponent
teams and other areas. Once this is signed off by all teams that
build is released to manufacturing - the actual point of RTM. It is
entirely possible for an escrowed build to be used for a number of
days or longer before all teams sign off on the build, its existence
does not mean a product has RTM'd only that it may well do so.
It should be noted that it is not a build number driven to RTM
quality - the product is driven to a build that can be agreed to be
signed off by all concerned. The build number is of little relevance
as that can be bumped and incremented arbitrarily for prior to release
of the code to pressing (as has been done in the past on other Windows
operating systems).
 
It's not RTM. Someone got the bogus idea that 6000 (which the Vista team
reached in build number) was a magic number... kind of like how we
Christians thought Jesus would return at the nice round number of year 2000.

Jon
 
Ah well, that straightened that one out...

Mike said:
Andre,

RTM is not handled as a forked process like the Beta builds. Once the
RTM push is under way post the RC builds, the build is not forked.
The main branch is pushed forward to a build that is effectively
escrowed as the RTM, it then undergoes more rigorous testing and any
changes required are built and applied to produce a new escrow, but
these should be rare at this stage after the huge number of test
cycles and builds released both publicly and to the tech beta program
and also released internally and to other programs and test sources.
Ultimately a build is escrowed and then tested by all subcomponent
teams and other areas. Once this is signed off by all teams that
build is released to manufacturing - the actual point of RTM. It is
entirely possible for an escrowed build to be used for a number of
days or longer before all teams sign off on the build, its existence
does not mean a product has RTM'd only that it may well do so.
It should be noted that it is not a build number driven to RTM
quality - the product is driven to a build that can be agreed to be
signed off by all concerned. The build number is of little relevance
as that can be bumped and incremented arbitrarily for prior to release
of the code to pressing (as has been done in the past on other Windows
operating systems).
Click to expand...
 
Back
Top