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

[Volker Simonis]

On Tue, Jun 17, 2025 at 4:21 PM Magnus Ihse Bursie
<magnus.ihse.bursie at oracle.com> wrote:
>
>
> 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).

OK, I see now, https://openjdk.org/groups/build/doc/building.html uses
iframe magic and https://htmlpreview.github.io under the hood to serve
the actual file as HTML. But this only the correct build.html file for
the master branch and not for the older release branches.So why do we
need this indirection through
https://openjdk.org/groups/build/doc/building.html and can not place
the link to https://htmlpreview.github.io/?https://raw.githubusercontent.com/openjdk/jdk/master/doc/building.html
right into the README.md file as I proposed? This would allow us to
point to the correct build.html in a branch while currently e.g. the
link in https://github.com/openjdk/jdk/blob/jdk23/README.md will show
us https://raw.githubusercontent.com/openjdk/jdk/master/doc/building.html
instead of the correct (and different)
https://raw.githubusercontent.com/openjdk/jdk/jdk23/doc/building.html.

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