Follow-up: Branch github.com/openjdk/jdk for stabilization (instead of fork)

[Magnus Ihse Bursie]

On 2025-06-16 18:35, Volker Simonis wrote:
> On Mon, Jun 16, 2025 at 12:07 PM Magnus Ihse Bursie
> <magnus.ihse.bursie at oracle.com> wrote:
>> What links are you referring to?
> Sorry for the confusion. I just realized that the links to
> `doc/building.{md,html}` are relative links and  therefor already
> pointing to the correct files.
>
> However, the link to the `online documentation` is pointing to
> `https://openjdk.org/groups/build/doc/building.html` which isn't even
> at GitHub but on openjkd.org and I don't know when and how that is
> updated (in any case, it's currently just a single, static file for
> all JDK versions). Instead, I propose to replace the link by something
> like https://htmlpreview.github.io/?https://github.com/openjdk/jdk/blob/jdk25/doc/building.html
> which will serve the current file as HTML and make it always
> up-to-date. Actually, once we have that, we could even remove the link
> to `https://github.com/openjdk/jdk/blob/jdk25/doc/building.html`
> because looking at a raw HTML file is pretty inconvenient if you're
> searching for build information.

Well, that is just what 
https://openjdk.org/groups/build/doc/building.html is. It is not a 
static page, it is a stable and comprehensible URL that gets the build 
README directly from Github (but presented as text/html from the server, 
which is something Github does not do). It is by purpose under 
openjdk.org, instead of pointing to Github, in the same vein as 
git.openjdk.org is used, instead of github.com, in official links.

As for the update branches, just having a relative path to the markdown 
file seems fine, and sufficient. (Long term, I want to remove the 
checked-in html versions and just keep the markdown versions, but there 
are some issues with markdown differences between GitHub and pandoc that 
needs to be resolved first, and this has not been a priority for me.)

/Magnus