[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-2d-dev
Subject:    [OpenJDK 2D-Dev] JDK 11 RDP1 and the jdk/client repository
From:       Philip Race <philip.race () oracle ! com>
Date:       2018-06-25 22:26:00
Message-ID: 5B316BF8.7030500 () oracle ! com
[Download RAW message or body]

I want to make sure people understand some of the nuances of RDP1 for 
JDK 11 [1]

- Any fix pushed to jdk/client after 2am PT Tue 26th June will be 
destined for JDK 12. Not JDK 11

- That is because this is the time we start the build for the final JDK 
11 Client PIT
   (PIT == Pre-Integration Testing), since changes need to be in jdk/jdk 
by Wed 27th.

- JDK 11 P1-P3 bugs may still be fixed after that date by pushing 
*directly* to the JDK 11
   stabilisation forest, which will be created after the fork. So if you 
have a fix for JDK 11 that
   misses 2am on the 26th you will need to wait for the stabilisation 
forest to open before pushing it.

- Fixes pushed to the JDK 11 stabilisation forest will be automatically 
synced to JDK 12 for some time,
    so if you want to fix something in 11 during RDP1, you do not need 
push it to jdk/client first,
    in fact you should not, because it is expected to be forward synced.

- Because there is only ONE stabilisation forest for all JDK 11, and NO 
further JDK 11 client PITs,
  it means the onus will be on the fixer to make sure they
    + do not break the build
    + do not introduce any regressions.
    + are fixing only bugs that really need to be in JDK 11 (proper use 
of P1-P3).

-phil.

[1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001462.html

[Attachment #3 (text/html)]

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I want to make sure people understand some of the nuances of RDP1
    for JDK 11 [1]
    <br>
    <br>
    - Any fix pushed to jdk/client after 2am PT Tue 26th June will be
    destined for JDK 12. Not JDK 11
    <br>
    <br>
    - That is because this is the time we start the build for the final
    JDK 11 Client PIT
    <br>
       (PIT == Pre-Integration Testing), since changes need to be in
    jdk/jdk by Wed 27th.
    <br>
    <br>
    - JDK 11 P1-P3 bugs may still be fixed after that date by pushing <b
      class="moz-txt-star"><span class="moz-txt-tag">*</span>directly<span
        class="moz-txt-tag">*</span></b> to the JDK 11
    <br>
       stabilisation forest, which will be created after the fork. So if
    you have a fix for JDK 11 that
    <br>
       misses 2am on the 26th you will need to wait for the stabilisation
    forest to open before pushing it.
    <br>
    <br>
    - Fixes pushed to the JDK 11 stabilisation forest will be
    automatically synced to JDK 12 for some time,
    <br>
         so if you want to fix something in 11 during RDP1, you do not
    need push it to jdk/client first,
    <br>
         in fact you should not, because it is expected to be forward
    synced.
    <br>
    <br>
    - Because there is only ONE stabilisation forest for all JDK 11, and
    NO further JDK 11 client PITs,
    <br>
      it means the onus will be on the fixer to make sure they
    <br>
         + do not break the build
    <br>
         + do not introduce any regressions.
    <br>
         + are fixing only bugs that really need to be in JDK 11 (proper
    use of P1-P3).
    <br>
    <br>
    -phil.
    <br>
    <br>
    [1] <a class="moz-txt-link-freetext"
href="http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001462.html">http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001462.html</a>
  </body>
</html>



[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic