G
Guest
I wanna know what RTM is short for? and what's the difference between it and
the full version of Win Vista?
thnx
the full version of Win Vista?
thnx
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Q
Quilljar
Hussein said:I wanna know what RTM is short for? and what's the difference
between it and the full version of Win Vista?
thnx
RTM is short for RTFM...
S
Steve Thackery
Release To Manufacture, which is the version you can go out and buy.
Steve
Steve
W
...winston
RTM = release to manufacturing = the final version of a new msft product for use in a commercial environment by stores, system builders, or pc manufacturers with the intent of distribution to the customer.
All current upgrade and full versions of Vista(as an example) are RTM.
:I wanna know what RTM is short for? and what's the difference between it and
: the full version of Win Vista?
:
: thnx
All current upgrade and full versions of Vista(as an example) are RTM.
:I wanna know what RTM is short for? and what's the difference between it and
: the full version of Win Vista?
:
: thnx
J
Julian
Quilljar said:RTM is short for RTFM...
;-)
R
Roy Coorne
Steve said:Release To Manufacture, which is the version you can go out and buy.
Steve
RTM (Release to manufacture) is the version which is forwarded to the
manufacturers; it is the final version which has 'gone gold' (i.e.
will yield income).
What you buy is RTM + key + wrapping or box...
Roy
T
Travis King
RTM stands for release to manufacturer and is one of the phases the
devolopment of software goes through. Specifically, it is the phase where
the software releases to manufacturers (the final release) so they can get
drivers prepared for the software. For example, Windows Vista went to RTM
status on November 8, 2006, but manufacturers had several months to prepare
and finalize some drivers for Vista before consumers actually got it on
January 30, 2007. Normally it goes like this for the major parts:
Alpha - This is the very early pre-stages of an operating system or software
where basically everything is considered concepts at this point and rarely
things stay the same from an Alpha build to a final build. Also, Alpha
builds are typically very unstable and often slow and definitely not worth
using for every day use.
Beta - This is the next major stage of software development. This is when
ideas normally start to come together and the software might actually
represent what it will look like in the final release. Often times, beta
software is still not very stable, has a lot of bugs, and is often times not
performance optimized, so in other words, the software is still a lot slower
than it will be in the final release.
Release Candidate - This is where things actually start to get polished.
Normally, the software is performance optimized for the most part by now, so
a release candidate is typically what actually is going to represent the
final release. You could also say for *most* software that the release
candidate is the build that is intended to be used for the final release
unless bugs are found. Yes, you often times will still find lots of bugs in
a release candidate.
devolopment of software goes through. Specifically, it is the phase where
the software releases to manufacturers (the final release) so they can get
drivers prepared for the software. For example, Windows Vista went to RTM
status on November 8, 2006, but manufacturers had several months to prepare
and finalize some drivers for Vista before consumers actually got it on
January 30, 2007. Normally it goes like this for the major parts:
Alpha - This is the very early pre-stages of an operating system or software
where basically everything is considered concepts at this point and rarely
things stay the same from an Alpha build to a final build. Also, Alpha
builds are typically very unstable and often slow and definitely not worth
using for every day use.
Beta - This is the next major stage of software development. This is when
ideas normally start to come together and the software might actually
represent what it will look like in the final release. Often times, beta
software is still not very stable, has a lot of bugs, and is often times not
performance optimized, so in other words, the software is still a lot slower
than it will be in the final release.
Release Candidate - This is where things actually start to get polished.
Normally, the software is performance optimized for the most part by now, so
a release candidate is typically what actually is going to represent the
final release. You could also say for *most* software that the release
candidate is the build that is intended to be used for the final release
unless bugs are found. Yes, you often times will still find lots of bugs in
a release candidate.
C
Colin Barnhorst
The Nov 8 release to manufacturing was to make the Business edition
available to enterprise customers (volume license and SA) by the end of
November. It actually had little to do with allowing devs to get drivers
ready for Vista release to the public in January. Driver developers and
Microsoft had been heavily engaged in that process for months before that.
The key releases for driver developers were the release candidates that
released during the five months prior to Nov 8, not rtm (build 6000).
available to enterprise customers (volume license and SA) by the end of
November. It actually had little to do with allowing devs to get drivers
ready for Vista release to the public in January. Driver developers and
Microsoft had been heavily engaged in that process for months before that.
The key releases for driver developers were the release candidates that
released during the five months prior to Nov 8, not rtm (build 6000).