Relationship of aarch32-port to jdk8u
Simon Nash
simon at cjnash.com
Thu Nov 3 21:38:31 UTC 2016
Andrew Hughes wrote:
>
> ----- Original Message -----
>> Hi Simon,
>>
>> On Sun, 2016-09-25 at 19:58 +0100, Simon Nash wrote:
>>> If I build the current source in aarch32-port, what level of jdk8u
>>> am I getting? I presume this is a snapshot from some point in the past
>>> but I'm not sure how to find out how long ago the snapshot was taken.
>> The aarch32 port is merged up to jdk8u102-b14, whereas the jdk8u-dev tip is
>> at jdk8u22-b01.
>>
>
> I'd regard this as a good thing, because jdk8u102-b14 is the last release.
>
> The jdk8u-dev tree is a combination of multiple upcoming releases. Oracle
> start work on one release (now u122), and collect community patches along
> with their own. At some point, they enter a second stage where they develop
> the release in a private branch and work on jdk8u-dev moves onto the next
> release. The final release then appears at the same time as the next
> security release. The final u122 won't appear until January 2017.
>
> With aarch64/jdk8u, we only merge up to the last release, so it is also
> currently at jdk8u102-b14. At security release time, we add first the
> latest security update (in July, this was u101) and then the latest
> feature update (u102 in July). We don't merge 8u in its entirety so
> we have something that can be shipped to end users.
>
> Unless the aarch32 project really needs the latest changes from 8u-dev,
> I would strongly suggest keeping to a similar model of just merging
> the latest feature release every three months.
>
As jdk8u111-b14 and jdk8u112-b15 have now been released by Oracle, will the
aarch32-port/jdk8u repo be updated to the jdk8u112-b15 level?
Simon
>> All the best,
>> Ed.
>>
>>
>
> Thanks,
More information about the aarch32-port-dev
mailing list