<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>On 2025-06-13 16:32, Volker Simonis wrote:</p>
<blockquote type="cite" cite="mid:CA+3eh13F+j-rHD+TMKX98Cr4DmpTK04zvg=gFOS+LDenKYXRyg@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">2. The new stabilization branches have the same, unmodified README.md
file like the main branch which is a little confusing. I propose that
every time we create a new stabilization branch the first change in
that new branch should update the README.md file (similar to what the
community updates repositories are already doing [5]) with at least
the following changes:
- "Welcome to the JDK!" -> "Welcome to the JDK <NN>!"
- Add a link to the corresponding release page (i.e.
<a class="moz-txt-link-freetext" href="https://openjdk.org/projects/jdk/">https://openjdk.org/projects/jdk/</a><NN>/)</pre>
</blockquote>
<p>That sounds like a very good idea. In fact, I think we should add
even more, like a text saying that this branch will be frozen
after GA, that mainline development will happen on the master
branch, and that further development on JDK NN will happen within
the JDK Updates project.<br>
</p>
<p><span style="white-space: pre-wrap">
</span></p>
<blockquote type="cite" cite="mid:CA+3eh13F+j-rHD+TMKX98Cr4DmpTK04zvg=gFOS+LDenKYXRyg@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">- The links to the build instructions should be changed to point to
the build instructions in the corresponding branch otherwise they
might eventually point to a newer, incompatible version</pre>
</blockquote>
<p>What links are you referring to?</p>
<blockquote type="cite" cite="mid:CA+3eh13F+j-rHD+TMKX98Cr4DmpTK04zvg=gFOS+LDenKYXRyg@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">
3. The last one is more of a usability issue and I currently don't
know how to solve it, but maybe someone else has an idea? Recently,
GitHub changed the sorting order of branches in the pull-down menu for
selecting a branch on their web page from alphabetical to "last
recently used" [3]. This now makes it almost impossible to find the
stabilization branches because they are buried somewhere in the middle
of a ton of "pr/xxxx" branches.</pre>
</blockquote>
<p>There is a search box in the drop down menu (at least for me, it
might be some A/B testing change?). Typing "jdk" there filters out
just the release branches. Not ideal, perhaps, but good enough.
Let's hope GitHub adds some way to "favorite" branches to have
them always show up first in the future.</p>
<p>/Magnus</p>
</body>
</html>