Preparation of update releases (original) (raw)

Volker Simonis volker.simonis at gmail.com
Tue Oct 23 16:55:18 UTC 2018

On Fri, Oct 19, 2018 at 5:43 PM Martin Buchholz <martinrb at google.com> wrote:

$ hg log -r '"jdk-11+28"::"jdk-11.0.1+13" and not file(.hgtags)' yields 7 changesets

Yes, but I don't think these 7 changesets are helpful in any way:

8209806: API docs should be updated to refer to javase11 8210432: Add additional TeliaSonera root certificate 8210345: The Japanese message of FileNotFoundException garbled 8209916: NPE in SupportedGroupsExtension 8210846: TLSv.1.3 interop problems with OpenSSL 1.1.1 when used on the client side with mutual auth 8211107: LDAPS communication failure with jdk 1.8.0_181 8211731: Reconsider default option for ClassPathURLCheck change done in JDK-8195874

These are the changes which are descendants of "jdk-11+28" and ancestors of "jdk-11.0.1+13" and I dont see how this query can help to answer either of the two questions "Which non-security changes were part of jdk-11.0.1+13" and "Which are all the new changes (i.e. security + non-security) introduced by "jdk-11.0.1+13" compared to "jdk-11+28".

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".

Looking at the graph of jdk-updates/jdk11u with "hg view" will easily illustrate the situation.

Regards, Volker

More information about the jdk-updates-dev mailing list