build number

[Henri Gomez]

> Hi, Henri,
>
> build number is a tag assigned by JDK release team when the build is
> released. MacOSX port is not merged with the main JDK workspace yet, so we
> don't have any promoted builds, so there are no build numbers.

I understand

> Consider the following scenario. Somebody clones the forest and runs "hg
> update -r jdk7-b132" to update the workspace to the state that corresponds
> to JDK7-b132 and then changes a single line in some class or native code. Is
> it still b132? Even if no files are touched, the build may and most likely
> will not be the same as JDK7-b132 promoted build as the build environment is
> different.

Exact, the idea was to give some advice to users about the possible
'build id' in version.
ie: something like build 1.7.0-internal-b136

I see where it could be updated, ie Defs.gmk, but wonder if it's the
correct way to do this.