Regular sync-ups from the upstream?
mike.duigou at oracle.com
Tue Feb 19 10:03:25 PST 2013
I plan to sync lambda with JDK8 mainline Wednesday following the next lambda promotion. I can also try do a sync with JSR 166 though am a bit nervous about potentially destabilizing patches in hotspot. Would you happen to have a changeset? It would save time.
We are very much trying to reduce the scope and number of differences between JDK8 mainline and the lambda repo at this point. If there was a way to get the changes in to JDK mainline quicker then I would prefer to use that route. Regardless, I am still willing to do this sync.
On Feb 18 2013, at 00:48 , Aleksey Shipilev wrote:
> Hi guys,
> It seems the lambda/lambda is the frontier of concurrency development
> these days. Both Doug had locked jsr166 to be compilable with the latest
> lambda/lambda, and me as well locked java-concurrency-torture to be
> compilable with the latest promoted build of jdk8-ea-lambda. (These
> address compilation of all these fancy lambda-enabled APIs).
> With the headlines like that, I'm going to ask regular sync-ups with the
> upstream to bring more goodness from regular channels, including
> non-lambda-specific j.u.c.*/HotSpot changes. Many of j.u.c. changes are
> pushed directly into jdk8.
> Example: @Contended already accessible in jdk8-b75 (promoted Jan 31),
> but not accessible in jdk8-lambda-b76 (promoted Feb 05?),
> jdk8-lambda-b77 (promoted Feb 11?).
> Maybe I'm missing some part of the plan to integrate lambda/lambda to
> upstream jdk8 completely, which will move the development back to
> mainline, and the whole issue would be nilled out.
More information about the lambda-dev