From dalibor.topic at oracle.com Wed Jan 10 00:08:23 2024 From: dalibor.topic at oracle.com (Dalibor Topic) Date: Wed, 10 Jan 2024 01:08:23 +0100 Subject: =?UTF-8?Q?Re=3A_OpenJDK_Committers=E2=80=99_Workshop=2C_2_February_?= =?UTF-8?Q?2024?= In-Reply-To: References: <20231222134427.18DA365230B@eggemoggin.niobe.net> Message-ID: <0d6f4b0d-6a02-4111-bc85-ee2f0e6165ea@oracle.com> Hi Johannes, Closing the loop here: thank you for reporting it, apparently the issue was fixed rather quickly. Registrants are receiving their confirmations. If a Committer happened to send an e-mail to register that didn't receive a reply yet, please do resend it, though. cheers, dalibor topic On 22.12.2023 15:04, Bechberger, Johannes wrote: > There seems to be a problem with the mail server: -- Dalibor Topic Consulting Product Manager Phone: +494089091214 , Mobile: +491737185961 Oracle Global Services Germany GmbH Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRB 246209 Gesch?ftsf?hrer: Ralf Herrmann From chegar999 at gmail.com Wed Jan 24 12:06:00 2024 From: chegar999 at gmail.com (Chris Hegarty) Date: Wed, 24 Jan 2024 12:06:00 +0000 Subject: Workshop topic: Archive of JDK EA tagged binaries Message-ID: <53fda3dc-1bdd-4e27-962b-dc51d925f9ed@gmail.com> Hi, I would like to propose the following topic for the workshop: Title: Archive of JDK EA tagged binaries Abstract: Projects that keep up to date with the latest JDK releases, e.g. upon release immediately adopt JDK 21, then 21.0.1, then 21.0.2, then 22, etc, would benefit greatly from archived tagged builds. For mainline EA releases, these builds are available throughout the development cycle, but no archive is available. For update releases, the benefit of EA testing is somewhat less valuable since the CPU fixes are not available until post GA, but still EA testing can catch non-CPU related issues. An archive is beneficial as it significantly improves the ability to track down development-time bugs (before they are shipped), both in terms of: 1. performing a bisect to narrow down when a bug or change in behaviour was introduced, and 2. allowing non-JDK savvy devs to track down a bug or change in behaviour Both the above can be done by doing self-builds, but this takes much longer and is not something that the average (!) Java dev is comfortable doing. Finally, the model of adopting the latest JDK is fantastic for moving the platform and ecosystem forward, let's support it in whatever way we can. Length: short Biography: Chris Hegarty, OpenJDK and Lucene committer, Software Engineer at Elastic Thanks, Chris. [*] Adoptium has some limited support for update release nightlies.