Closed andrew-m-leonard closed 3 years ago
@karianna fyi
Has it been considered to contribute this to OpenJDK upstream?
No, Interesting point, but wondering why Oracle, Azul, et al have not contributed their ones....?
Not sure why this hasn't been done by others, yet. Getting a discussion started could potentially answer some of those questions. I'd encourage you to start a discussion about this upstream and get some opinions. Perhaps jdk-dev would be a good place? Failing upstream acceptance would make a better case for contributing it to AdoptOpenJDK, fwiw.
i'll give it a go on jdk-dev and see what response I get...
Thanks, @andrew-m-leonard!
@andrew-m-leonard is the code already available somewhere? I would love to see how you do the JDK scan since we create similar functionality in https://github.com/AdoptOpenJDK/IcedTea-Web and https://github.com/karakun/OpenWebStart
@hendrikebbers not yet... we have to do the due diligence on scanning and licensing etc beforehand
So as was highlightd in the openjdk jdk-dev thread there are several issues with the above approach, in particular:
OpenJDK is currently at the latest IANA release 2019c. As an alternative approach, I would like to suggest the idea of doing ".1" releases with updated IANA data, via an AdoptOpenJDK patch, if a scheduled Qtrly release is say over 1 month away(?).. The patch can then be contributed upstream, if not already been done. In this way we can "react" quickly to a new IANA release, just like if a sev1 security update might be...
Raised TSC issue to discuss proposal: https://github.com/AdoptOpenJDK/TSC/issues/156
Am presuming that this can be closed in favour of #156
We would like to contribute a fully functioning JDK Timezone updater to AdoptOpenJDK, along with supporting build&test pipelines for it. In summary the tool provides the following:
Updater tool is pure java and runs with any JDK8+.