understanding Chrome OS code version numbering

[Trever]

I'll break this out into another thread...

Can anyone explain if the versioning we see in Chrome OS follows the Chrome versioning conventions described here:

http://www.chromium.org/releases/version-numbers

Yes?  No?

More detail if necessary:

For obvious reasons, it seems the conventions can't be identical because the second two codes bases of Chrome OS version strings lack the last field, they look like this (for me currently):

Version 25.0.1364.126

Platform 3428.193.0 (Official Build) stable-channel stumpy

Firmware Google_Stumpy.2.102.0

Is there a convention of leaving off the last field (the patch level) if it is zero?

And just FYI, correct me if I'm wrong but I'm given to understand that:

Version refers to Chrome browser code base

Platform refers to Linux portions (disc image) code base

Firmware refers to code base that's burned onboard hardware and RW firmware written to disc (portions of it)

There's probably room for clarification there too...

Sorry if this is mundane but I'm *very* curious to understand this.  I haven't found the information so far in my searching around (including source code), sorry if I've missed it.

Thanks in advance,

Trever

[Mike Frysinger]

ChromeOS has the same major number as Chrome. it's just implicit.

the first # is incremented on ToT for every major build (about 4 times
a day). the second # is incremented on the branch once per build
(which is why ToT is always .0.). the final number is when we have to
do a weird thing like branch a branch. it doesn't happen too often.

the firmware now follows the same convention. the stumpy/lumpy might
not be exact because they were the first boards where we did the
firmware all ourselves and the process hadn't exactly solidified. i'm
guessing at this last bit because it predates me.
-mike

> --
> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
>
>
>

[Mike Frysinger]

i'll update the public docs. we have an internal doc, but it is
outdated and refers to how we did things before R16. wheeeeee.
-mike

[Trever]

Ah, okay.  I think I did hear once about implicit major number, come to think of it.

Re public doc, excellent!   Thanks Mike.

ToT?  Stands for?  Top of tree?

[Mike Frysinger]

On Tue, Mar 5, 2013 at 4:30 PM, Trever <trr...@gmail.com> wrote:
> Ah, okay. I think I did hear once about implicit major number, come to
> think of it.
>
> Re public doc, excellent! Thanks Mike.

http://www.chromium.org/releases/version-numbers should be updated now

> ToT? Stands for? Top of tree?

usually tip of tree
-mike