This proposal has been approved and the Eclipse Temurin® project has been created.
Visit the project page for the latest information and development.

Eclipse Temurin

Wednesday, November 11, 2020 - 09:09 by Tim Ellison
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Parent Project
Proposal State
Created
Background

The AdoptOpenJDK project was established in 2017 following years of discussions about the general lack of an open and reproducible build and test system for OpenJDK source across multiple platforms. Since then it has grown to become a leading provider of high-quality OpenJDK-based binaries used by enterprises in embedded systems, desktops, traditional servers, modern cloud platforms, and large mainframes.

The Eclipse Adoptium top-level project is the continuation of the original AdoptOpenJDK mission at the Eclipse Foundation.  The Adoptium project encompasses all aspects of the AdoptOpenJDK project, and that single endeavor is being constructed at Eclipse across projects such as Temurin and AQAvit.

Scope

The scope of the 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.

Description

The 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-source licensed, and Java SE TCK-tested for general use across the Java ecosystem.

Why Here?

Eclipse has a long history of Java SE-based projects. Temurin brings the capability to produce an Eclipse community built runtime that is readily accessible to Eclipse projects and users that fits their purpose. It also provides the community with an accessible focal point for defining the Java SE runtime capabilities that they require.

Future Work

The dynamic plan is available on-line here:

https://github.com/orgs/AdoptOpenJDK/projects/1

Project Scheduling

The usual schedule for the AdoptOpenJDK project is to release quarterly, in line with the upstream OpenJDK calendar.  That would be January, April, July, and October.

Given the additional requirements to comply with the Eclipse processes, we would expect the first release to be one full quarter after the project moves to the Foundation.

Committers
Simon Rushton (This committer does not have an Eclipse Account)
Hendrik Ebbers (This committer does not have an Eclipse Account)
John Oliver (This committer does not have an Eclipse Account)
Morgan Davies (This committer does not have an Eclipse Account)
Will Parker (This committer does not have an Eclipse Account)
Initial Contribution

AdoptOpenJDK code will be used as the initial contribution.

The copyright of such code is spread across the community of contributors, which includes a variety of individuals and companies.

Source Repository Type