| Author |
Topic |
|
|
akidder
1519 Posts |
 Posted - 06 Sep 2005 : 19:01:52
|
ADS Windows CE Build Numbering
ADS gives a unique number to every CE build it releases. This allows ADS to identify builds for configuration management, test and troubleshooting purposes.
The Release Number Format
The format of the release number is
m.mm.bbb ccc-ddd (e.g. 4.20.32 PRO-RAM)
where
m.mm is the Microsoft kernel release (e.g. 4.20 for CE 4.2)
bbb is the ADS build number
ccc specifies the licensing model (CORE, PROfessional, PROPLUS Professional-Plus)
ddd specifies the registry driver uses (RAM- or HIVE-based)
The ADS Development Process
The ADS CE build process is as follows:- Our development team makes changes to the drivers for one or more platforms, testing driver changes on their local computers.
- The driver changes are uploaded to our version control system, then downloaded into a central build machine.
- We increment the ADS build number ("bbb").
- We create a new CE build, compiling the new drivers and assembling them into a CE binary image.
- The new CE image goes to our validation lab, where we run the build through a series of standard tests to verify that all drivers meet our specifications.
- If the build fails validation, the process returns to Step 1 to make corrections.
- If the build passes validation, it moves on to our configuration management, where it is assigned an ADS part number (format: 700xxx-xxxxx).
- The CE build is released to our developers site and details about the changes are posted on the appropriate forum page.
Gaps in the Build Histories?
In the build numbering system that ADS uses, it may appear that there are gaps in the releases. These gaps are natural, as they represent the several rounds of test and validation that occur before a build is released.
Release Candidates (Beta Builds)
Sometimes we make release candidate CE builds available to you, our customers, before the build has completed validation. In these cases, the build is assigned an ADS part number after Step 3 and given directly to you. We will let you know that the release candidate has not yet been formally tested or released, but give you the opportunity to test the changes in parallel with our validation team.
In many cases, beta builds will be formally released a short time later after you receive them. This "parallel processing" helps accelerate your product development.
Previous ADS Build Numbering Systems
ADS has used three other build numbering schemes in the past.
1. In the days of CE 3.0 and 4.0, ADS used the format m.vv, where the "m" was a "3" or "4" representing CE 3.0 and CE 4.0, respectively, and vv was the sequential ADS build number.
2. Around the time that CE 4.1 and 4.2 were released, ADS adopted a new numbering scheme to account for the additional digits in the Microsoft releases. The new format was m.mm.vv where m.mm was "4.10" or "4.20" for the Microsoft kernel release, and vv was the sequential ADS build number. Details are posted at topic 1781.
Note that some 4.10 builds used the original m.vv (4.vv) format. To determine if they are 4.0 or 4.1 CE builds, see the debug port output.
3. Between fall 2004 and summer 2005, we used the m.mm.vv.bb format described in topic 1853. We have since dropped the extra digits and returned to a simpler format. |
|
|
Instron
8 Posts |
Posted - 27 Sep 2005 : 07:12:58
|
| How do you retrieve the build number programmatically? I use the function GetVersionEx() and the correct major & minor versions are returned. However, the build number is always 0. |
 |
|
|
Susan
123 Posts |
|
| |
Topic |
|
|
|
All Forums
Microsoft Windows CE
ADS Windows CE Build Numbering
Forum Locked
Topic Locked
Send Topic to a Friend
Printer Friendly