JDK11u repository and tagging

[Ludovic Henry]

Hi,

As we are trying to have testing and releasing of riscv-port-jdk11u
<https://github.com/openjdk/riscv-port-jdk11u/> at Adoptium, we are running
into the issue that the way we are tagging this repo is inconsistent with
jdk11u-dev <https://github.com/openjdk/jdk11u-dev> (see
adoptium/temurin-build#3911
<https://github.com/adoptium/temurin-build/issues/3911> for more details)
For example, the latest merge from `jdk11u-dev:master` into
`riscv-port-jdk11u:riscv-port` with eff8723
<https://github.com/openjdk/riscv-port-jdk11u/commit/eff8723c422034551021d9472a6ccc5e3aab3df8>
merges jdk-11.0.25+2
<https://github.com/openjdk/jdk11u-dev/tree/jdk-11.0.25%2B2> but no
equivalent tag is created on eff8723
<https://github.com/openjdk/riscv-port-jdk11u/commit/eff8723c422034551021d9472a6ccc5e3aab3df8>
.

Taking aarch32-port-jdk8u <https://github.com/openjdk/aarch32-port-jdk8u>
as an example, the solution has been to tag the merge of the jdk8u-dev tag
with an equivalent name. For example, the merge commit
<https://github.com/openjdk/aarch32-port-jdk8u/commit/0a8022e9baf793caf88a61f6ce99cd6a3531b56e>
of `jdk8u422-ga` is tagged with `jdk8u422-ga-aarch32-20240725`.

Fei, I understand you've been doing it. Has it been a manual process for
you? Are you looking at automating some of the merging process?

Thanks,
Ludovic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/riscv-port-dev/attachments/20240816/4b2b1b9d/attachment.htm>