Test Embedded : CE 6.0 - why the codename "Yamazaki" ?

 

CE 6.0 - why the codename "Yamazaki" ?

I've been asked why we used the name "Yamazaki" as a codename for CE 6.0 - There's some history behind the naming of Windows CE versions, here's the short version...

Before the Windows CE product was released we had an internal set of tools known as the Oem Adaptation Kit also known as the OAK - an OAK of course is a type of tree.

The initial releases of Windows CE were therefore named after trees, as follows.

• Windows CE 1.0 - Alder (Nov 1996)
• Windows CE 2.0 - Birch (Nov 1997)
• Windows CE 3.0 - Cedar (Apr 2000)

Interestingly, there was a second team within the Windows CE group that worked on the tools, I guess you could consider tools to be something that makes a job easier, or cuts the job down to size - therefore the tools releases were named after things that cut down trees  - as follows...

• Windows CE 1.0 - Alder - Tools: Axe
• Windows CE 2.0 - Birch - Tools: Buzzsaw
• Windows CE 3.0 - Cedar - Tools: Chainsaw

For Windows CE 4.0 the original plan was to call the O/S DougFir (DouglasFir), the thing that cuts down DougFir trees was going to be Dozer (BullDozer) - interestingly, at Windows CE 4.0 the o/s team and tools teams merged together to form a new, combined team - the codenames for the operating system and tools also changed at this time from trees/tools to <drumroll>Whiskeys</drumroll> - so the codenames for Windows CE 4.0 onwards are as follows.

• Windows CE 4.0 - Talisker (Jan 2002)
• Windows CE 4.1 - Jameson (Jun 2002)
• Windows CE 4.2 - McKendric (Apr 2003)
• Windows CE 5.0 - Macallan (Aug 2004)
  • Windows CE 5.0 Network Device Feature Pack - Tomatin (Apr 2006)
• Windows CE 6.0 - Yamazaki (Sep 2006)

Don

*originally posted on Mike Hall's Weblog

Published Friday, September 29, 2006 9:33 AM by wceqalab

Test Embedded : CE 6.0 - why the codename "Yamazaki" ?