<story><title>Mystery meat OpenJDK builds strike again</title><url>https://mail.openjdk.java.net/pipermail/jdk8u-dev/2019-May/009330.html</url></story><parent_chain></parent_chain><comment><author>CaliforniaKarl</author><text>A few emails later in the thread[0], it is noted...&lt;p&gt;&amp;gt; ...who actually maintains the &amp;quot;official&amp;quot; Docker images for 8u and 11u? Github history for
Dockerfiles points to no one I recognize from around OpenJDK.&lt;p&gt;That, I think, is the main problem.&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;mail.openjdk.java.net&amp;#x2F;pipermail&amp;#x2F;jdk8u-dev&amp;#x2F;2019-May&amp;#x2F;009335.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;mail.openjdk.java.net&amp;#x2F;pipermail&amp;#x2F;jdk8u-dev&amp;#x2F;2019-May&amp;#x2F;0...&lt;/a&gt;&lt;p&gt;Edit: Actually linking to source (which I should&amp;#x27;ve done from the beginning…)</text></comment>
<story><title>Mystery meat OpenJDK builds strike again</title><url>https://mail.openjdk.java.net/pipermail/jdk8u-dev/2019-May/009330.html</url></story><parent_chain></parent_chain><comment><author>chungy</author><text>As an observer, not any kind of authority:&lt;p&gt;The release methodology of OpenJDK from Oracle is obscure at best, and it is hard to imagine how package managers are supposed to cope. I notice both of these examples come with Debian version strings attached, and they likely build from tags in the version control repository. As example, in these two links:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hg.openjdk.java.net&amp;#x2F;jdk8u&amp;#x2F;jdk8u&amp;#x2F;tags&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hg.openjdk.java.net&amp;#x2F;jdk8u&amp;#x2F;jdk8u&amp;#x2F;tags&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hg.openjdk.java.net&amp;#x2F;jdk-updates&amp;#x2F;jdk11u&amp;#x2F;tags&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hg.openjdk.java.net&amp;#x2F;jdk-updates&amp;#x2F;jdk11u&amp;#x2F;tags&lt;/a&gt;&lt;p&gt;The &amp;quot;-ga&amp;quot; tags do pretty clearly delineate official releases, but they also get pushed to the public repository well (often weeks) after Oracle posts official binaries for these releases. It is confusing and makes it not all that mysterious that distribution packaging will take the best that they can see for doing a clean build, as they like to do.&lt;p&gt;It would help quite a lot if the +1&amp;#x2F;+2&amp;#x2F;+3&amp;#x2F;etc releases were instead delineated with &amp;quot;-alpha1&amp;quot;, &amp;quot;-beta1&amp;quot;, &amp;quot;-rc1&amp;quot; tags. Much clearer that they aren&amp;#x27;t meant to be production.</text></comment>