Version strings and update build numbers (determining when an update release goes GA)

[Seán Coffey]

Martijn,

You raise a good point around how one can easily identify releases that 
have shipped. From an Oracle JDK perspective, the release notes should 
always state the final build number of the 'shipped' release. For now, 
that's probably the safest way to match a repo tag to a shipped JDK version.

Perhaps a JBS enhancement request can be logged to track improvements in 
this area. Would it make sense to add a new label to identify the final 
'shipped' release ? e.g. jdk8u131-b11-GA

Regards,
Sean.

On 23/05/17 15:19, Martijn Verburg wrote:
> Hi all,
>
> The Adopt OpenJDK community has created an OpenJDK Build farm
> <https://www.adoptopenjdk.net> for as many platforms as possible in order
> to assist with early testing of things like backported patches in jdk8u.
>
> We have a question on update and build numbers currently used in tags.
>
> At the moment we are picking up the version string from the tag
> 1.8.0u152-b04, but we're a bit hesitant at making an binary release of that
> particular tag as 1.8.0u152 isn't 'officially' released yet.
>
> Is there a way to automatically tell when the update version is 'done'?
> For example update 131 was released as jdk8u131-b11....
>
> Cheers,
> Martijn