Coordinating the build number for 11.0.3

Tue Apr 2 01:17:30 UTC 2019

On 30/03/2019 19:54, Langer, Christoph wrote:
> Hi Gil, Andrew,
> 
> I don't really like the idea to define the exact build number beforehand with leap space for additional builds.
> 
> However, I can see that it would be helpful for distributions that want to release a binary right at the release day without waiting for the public release of the CPU changes, then picking them up, merging, triggering builds and do regression testing. Doing so will obviously delay the availability of the binaries and incurs some uncalculatable risk regarding merging and regressions.
> 
> So, maybe we can agree that the final build number will always be the publicly visible build number + 1. Andrew, not knowing your exact processes regarding the handling of CPU changes, would you think you'd be able to commit to that?
> 
> Best regards
> Christoph
> 
> 
> 

No. I can guarantee that it won't be lower than that.

I don't see that as a problem, as a downstream version that patches
ahead of the unembargo will be able to use freeze version + 1, and can
sync to any later version once it is made public. Or, as Goetz says, use
your own tags.

Best regards,
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222
https://keybase.io/gnu_andrew