| 22 Mar 2026 |
 emily | the -ga tags are final releases https://github.com/openjdk/jdk11u/tags | 20:38:18 |
| emily | the update script should only update to those | 20:38:25 |
| emily | may be better to backport whatever was needed for the new glibc than to keep following a pre-release | 20:38:43 |
 Benedikt Ritter (britter) | Now that sheds some light! I agree we should not be following pre-releases. I wasn't aware of the details of the numbering scheme and assumed +x would mark some kind of patch version. | 20:49:40 |
| Benedikt Ritter (britter) | Maybe we should add a check that makes sure the tag name ends with -ga | 20:50:14 |
| Benedikt Ritter (britter) | @emilazy:matrix.org I've closed my PR. At the same time I don't see myself backporting a patch that fixes the glibc issue. If anybody else wants to give that a try, feel free. Or we'll just wait until ga is released. | 20:57:20 |
| emily | yeah, it's the most confusing numbering scheme around… | 20:57:45 |
| emily | the JSON files deliberately recall the full tag name to have the canonical version available | 20:57:53 |
| emily | but the update script only updates to final releases | 20:58:00 |
| emily | basically it counts up to +n and then they tag -ga at the same commit as +n | 20:58:38 |
