Eclipse Temurin®
Project state: Regular
Summary: The Eclipse Temurin® project provides code and processes that support the building of runtime binaries and associated technologies that are high performance, enterprise-caliber, cross-platform, open...

The scope of the Eclipse Temurin® project is to provide code and processes that support the building of runtime binaries that are high performance, enterprise-caliber, cross-platform, open-source licensed, and Java SE TCK-tested for general use across the Java ecosystem.

The project will implement and manage artifacts including infrastructure as code, and a comprehensive continuous integration (CI) build and test farm in conjunction with other projects under the Adoptium top-level project.

Participants in the project are responsible for developing, managing, promoting, and supporting technologies that:

Define the content of the runtime and development kit releases.

Manage full life-cycle releases of the binaries.

Develop build-scripts, installers, application programming interface (API), website, and infrastructure for runtime distribution.

Define the CI system pipelines and manage the CI system for security, efficiency, and purpose.

Respond to end-users and provide support as appropriate.

Be the principal technical interface to upstream technology projects.

Orchestrate the official distributions of the project releases, including website, archives, Docker, and others.

Provide usage stats to support the top-level project's marketing and buzz objectives.

In addition to providing a reliable source of contemporary Java runtime binaries, the Temurin project is a platform for experimentation by developers, academics, and researchers.
This project provides a place to try out new runtime, build, test, and infrastructure ideas. Examples of projects that fall under this scope include “jlink.online” for serving right-sized runtimes to application developers, “Github actions” to obtain and test applications with runtimes within Github’s workflow, “TKG” the test-kit generation framework, and “Bumblebench” the micro benchmarking framework.

Project leads: hebbers (Hendrik Ebbers), mverburg (Martijn Verburg), sgehwolf (Severin Gehwolf), tellison (Tim Ellison), gadamsuwr (George Adams), joliver77u (John Oliver), saddisonxls (Stewart Addison), slambertokd (Shelley Lambert)
Committers: wenzhou (Wen Zhou), scottfryer (Scott Fryer), pdoussot (Philippe Doussot), mdaviesd0f (Morgan Davies), wparkernpd (William Parker), afarley (Adam Farley), nebbitt (Nick Ebbitt), bappali (bharath appali), hebbers (Hendrik Ebbers), sguodfx (Sophia Guo), mverburg (Martijn Verburg), sgehwolf (Severin Gehwolf), srushton (Simon Rushton), tellison (Tim Ellison), gadamsuwr (George Adams), joliver77u (John Oliver), aleonardf4y (Andrew Leonard), saddisonxls (Stewart Addison), slambertokd (Shelley Lambert), dkeeler (Derek Keeler), hkhel45y (Haroon Khel)
Contributors: wenzhou (Wen Zhou), aixtools (Michael Felt), jkangrnn (Jie Kang)