ZBB not next week - jdk9/hs will not close

[Jesper Wilhelmsson]

Hi again!

We started to think about what ZBB means and how it will be managed in 
the HotSpot case where there is a two week delay between a fix being 
pushed and the fix reaching master. I'm happy to say that my previous 
interpretation was wrong.

The definition is that when all JDK 9 bugs created more than 5 [1] days 
ago 


are fixed, deferred, or in critical watch we reach ZBB.

This is a JBS measure and is unrelated to where a fix is located in our 
repository structure. This means that since a bug is closed when we fix 
it in hs, we are done in the ZBB point of view. We do not have to wait 
for the fix to reach master.

The conclusion is that we got two more weeks of bug fixing before ZBB. 
The ZBB date is the same regardless of where the fix is pushed - 
February 16.

There is no need to close hs for ZBB.

Cheers,
/Jesper

[1] 5 or 7 days depending on who you listen to. I expect a few more 
mails to pass before reaching a conclusion here.


On 2017-01-24 00:12, Jesper Wilhelmsson wrote:
> Hello HotSpot developers!
>
> The next JDK 9 milestone, Zero Bug Bounce (ZBB), is getting closer. All
> JDK 9 bug fixes for ZBB need to be in master (jdk9/jdk9) no later than
> February 16.
>
> As usual we need about two weeks to get from jdk9/hs through testing to
> jdk9/jdk9. This means that the last date to push a change to jdk9/hs
> will be February 1:st - Wednesday next week.
>
> The current plan is to close jdk9/hs for all pushes in the evening of
> Wednesday next week. This is done in order to allow for a few days of
> stabilization before I will start the integration work on Friday next week.
>
> The ZBB date and closing hs applies to all OpenJDK developers. Please
> sync with me if you need more time for your last ZBB fixes.
>
> For more information see the JDK 9 schedule on
> http://openjdk.java.net/projects/jdk9/
>
> Thank you for your co-operation!
> /Jesper
>
>
> Zero Bug Bounce (ZBB) — The bug backlog is completely addressed. No open
> bug with a fix targeted to the release is older than 24 hours, and other
> bugs have been deferred to a future release.