Preparation of update releases
Alan Bateman
Alan.Bateman at oracle.com
Tue Oct 23 17:14:48 UTC 2018
On 23/10/2018 17:55, Volker Simonis wrote:
> :
> Theproblem with this query is that the jdk-11.0.1 was cloned from
> jdk/jdk11 BEFORE jdk/jdk11 was tagged with "jdk-11+28". After its
> creation, a lot of changes (security- and non-security) were added to
> the jdk-11.0.1 repository (which are not descendants of "jdk-11+28"
> and thus will not show up in your query). Later, (on August 28th to
> be precise) the tag "jdk-11+28" from jdk/jdk11 was merged back into
> the jdk-11.0.1 (with changeset 51336:c2b23a17d3ff which was later
> tagged as "jdk-11.0.1+8"). Your query only shows changes (again, both,
> security and non-security) in the jdk-11.0.1 repo which happened AFTER
> this merge and before the jdk-11.0.1 repo was tagged with
> "jdk-11.0.1+13".
>
Have you tried the JBS as suggested in the other replies? You can use
that now to see the non-security changes in 11.0.1 and the changes
already integrated for 11.0.2. I've already found that easier than
trying to figure it out from the hg logs.
-Alan
More information about the jdk-updates-dev
mailing list