RFC: JEP JDK-8208089: Implement C++14 Language Features (original) (raw)
Aleksei Voitylov aleksei.voitylov at bell-sw.com
Wed Oct 17 20:50:30 UTC 2018
- Previous message (by thread): RFC: JEP JDK-8208089: Implement C++14 Language Features
- Next message (by thread): RFC: JEP JDK-8208089: Implement C++14 Language Features
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 16/10/2018 02:25, Kim Barrett wrote:
On Oct 15, 2018, at 7:51 AM, Aleksei Voitylov <aleksei.voitylov at bell-sw.com> wrote:
Kim, If you were suggesting to just proceed with the change without giving a sufficient lead time for the ports that were willing to upgrade to do so, that sounds very alarming. What is "sufficient lead time"? I'm not proposing an answer, just suggesting that 3 months (approx time between JEP publication and JDK 12 fork) might be sufficient, and a worthy goal. That's a decision that ought to be made as part of the Targeting discussion for this JEP. Right now, it's not even a Candidate, since there's still work to be done. I'm fine with that, and you probably can assume to document this goal in the JEP if noone speaks up. Meanwhile, our testing has finished and I'm now confident we will be able to switch ARM port over to 7.x in 12 time frame. There are several issues that we still need to diagnose, but this does not look like a blocker. That's good news, though pretty much what I expected. I'm more worried about Solaris. Having a goal of JDK 12 may help move things along.
- Previous message (by thread): RFC: JEP JDK-8208089: Implement C++14 Language Features
- Next message (by thread): RFC: JEP JDK-8208089: Implement C++14 Language Features
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]