Coordinating the build number for 11.0.3

[Gil Tene]

> On Apr 1, 2019, at 12:17 AM, Lindenmaier, Goetz <goetz.lindenmaier at sap.com> wrote:
> 
> Hi Gil,
> 
> I think you can never be sure that you don't need another
> build. Therefore you can not predict the final build number.
> See what happened with 11.0.2.

11.0.2 initially came out with an 11.0.2+7, and later (quickly)
updated to 11.0.2+9 (which, ironically, fixed a mistake in the
date in version string).

I am not expecting coordination to "save" us from a
"11.0.2+7 to 11.0.2+9 like", post-initial GA shift, as such
a change cannot be foreseen and would require re-testing
in any case. But I do want it to allow for a coordinated
"11.0.2+7 like" situation, so that tested binaries can be
primed to go with our best-guess version string in them.

My point is that we can avoid the "guess" part of the
best-guess by coordinating the build number that will be
used if no additional changes (other than in-the-dark
security fix integration) will occur.

I think that leaving room for 2-3 additional build numbers
[in order to deal with potential for multiple build number
increments during the eventual integration of security
updates] is one way to do that.

Alternately, carefully working to integrate all security
updates in a single shot (making sure that the build number
only increments by one) is another approach.

I'm good with either, I just want a target build number to
[speculatively] start tests on, and an understanding that
we want to aim for that build number actually being the
eventual build number (barring surprises) so that the
various binaries can end up with the same "11.0.3+42"
part of the version string of all goes well, without having
to re-spin and re-test after the upstream gets published.

> 
> I assume Andrew �� will push a -ga tag with the security
> changes, so that will be the one to go for.
> 
> Best regards,
>  Goetz.
> 
>> -----Original Message-----
>> From: jdk-updates-dev <jdk-updates-dev-bounces at openjdk.java.net> On
>> Behalf Of Gil Tene
>> Sent: Freitag, 29. März 2019 23:02
>> To: jdk-updates-dev at openjdk.java.net
>> Subject: Coordinating the build number for 11.0.3
>> 
>> As we approach the April update and the release of 11.0.3 by the
>> JDK11u project, I'd like to suggest a coordination of the eventual
>> build number that we expect to use for the actual released build in
>> the project (after integration of security fixes that are being worked
>> on in the dark).
>> 
>> Since the build number is a part of the versions string per JEP 322,
>> and since this is the most specific part of the version string that is
>> common across the various binary distributions (e.g.
>> Azul Zulu, AdoptOpenJDK, Corretto, Liberica, Red Hat, etc.), it
>> is useful for us all to use the same build number when we release
>> the first build of a new update of 11u. This has been the practice in
>> the past. E.g. for 11.0.2, we all aligned on the same "build 11.0.2+9"
>> in the version string.
>> 
>> Since the update itself is time sensitive, and it is useful to commence
>> testing ahead of time, knowing the build number to use in the builds
>> we test would be helpful in getting the builds ready to go ASAP once
>> the release is finalized.
>> 
>> So, I propose that we pre-choose a build number for the anticipated
>> April release of 11.0.3. I have no strong opinions on what that number
>> should be. It should probably not overlap with past or current builds of
>> 11.0.3 in 11u, and "leaving room" (a gap of a few integer spaces
>> between the current build numbers and the anticipated one) is probably
>> a good idea.
>> 
>> — Gil.