<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
All,<br>
<br>
Contingent on Project Skara (ie mercurial ->git / githib) going
active for the JDK project on schedule<br>
on 5th September, we intend to retire the jdk/client repo/forest as
part of this transition.<br>
<br>
In other words, once mercurial is shut down and we move to git there
will ONLY be the main JDK repo<br>
and all client pushes will go there.<br>
<br>
We will be making some internal testing changes which we hope will
help us spot any breakages<br>
that pushes cause in time to prevent them making their way directly
into a promoted build but they<br>
can't completely replace the manual testing we have been doing, so
we will also be<br>
dependent on folks to be extra diligent from now on and not assume
there is a gatekeeper<br>
who will spot their mistakes.<br>
<br>
But we do need some time to "flush" any last changes in client to
jdk before mercurial shuts down.<br>
<br>
So accordingly the ABSOLUTE LATEST DROP DEAD time for pushes to
jdk/client should be<br>
>> <font color="#ff0000">9am PDT Tuesday 1st Sept 2020</font>
<<<br>
<br>
Anything pushed after that time may be lost forever :-)<br>
<br>
We'll also further enforce this as of <font color="#ff0000">9am
PDT Wednesday 2nd Sept 2020 </font>by making the client repo<br>
mercurial repo <font color="#ff0000">read-only.</font> The 24 hours
is to help the integrator/gate keeper - not for your late pushes,<br>
For example if there's a breakage we need to back out before
integrating we might need this.<br>
So not even "doc" or "test" changes - nothing please !<br>
<br>
You may reasonably ask why then Tue/Wed for this if skara is not
transitioning until Sat 5th September ?<br>
The answer is that in an unfortunate coincidence of timing we have a
big lab move that begins around<br>
9am PT Wed 2nd September, and all our testing capabilities will be
off-line for several days.<br>
So any test jobs submitted after sometime Tuesday won't have time<br>
to complete, and the lab move won't be complete until after the
skara transition.<br>
<br>
Any outstanding reviews that don't make the cut-off will of course
have to be resubmitted as github pull requests<br>
and any approvals they may have accumulated will need to be
re-approved. All of this is of course true for<br>
folks pushing directly to the mercurial main JDK repo - it is not
related to the client repo retirement.<br>
<br>
-Phil<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>