Skip to main content

Roadmap

The Artemis roadmap is a GitHub project board, not a document. It is kept where the work actually happens, so a roadmap item and the pull requests that implement it are the same objects rather than two lists that drift apart.

Open the Artemis Roadmap board

How to read the board​

FieldMeaning
Status: ExploringBeing investigated. No commitment that it will be built.
Status: PlannedAgreed and scheduled for a target semester.
Status: In progressImplementation underway. For most items this means an open pull request.
Status: ShippedReleased. The release notes name the version.
AreaThe feature area, using the same vocabulary as pull request titles, so an item and the changes implementing it carry the same label.
TargetA semester, for example WS 26/27. Never a date.

Targets are semesters on purpose. Universities plan in semesters, a semester communicates intent without reading as a delivery date, and it matches how the project itself works: features land in time for a teaching period or they wait for the next one.

What is on it​

One-year direction​

For October 2026 through October 2027, the project intends to:

  • Complete the web client's migration to TUM AET UI and remove the superseded controls.
  • Strengthen scalable infrastructure, including build execution, distributed state, and deployment.
  • Simplify the supported infrastructure to LocalVC, LocalCI and PostgreSQL by removing Jenkins and MySQL in Artemis 11 (see Planned removals in Artemis 11).
  • Improve AI-assisted exercise authoring and feedback while keeping these features optional and under the institution's control.
  • Extend learning analytics while preserving data privacy.

These directions correspond to the work on the board. They are priorities for the planning horizon, not promises to deliver every item within it. The project does not commit to a hosted service, fixed delivery dates, or an LTS release during this horizon. The release and support policy continues to govern support and backport requests.

The weekly roadmap review checks both the individual items and this one-year direction. Before the horizon expires, maintainers extend it or publish its successor so that contributors can always see at least a year's intended direction and scope.

Planned removals in Artemis 11​

Artemis 11 is planned to ship in March 2027 (target semester WS 26/27). It removes two integrations that have a replacement and that cost a disproportionate amount of maintenance and test time:

RemovalReplacementStatus
Jenkins, the only external continuous integration system that Artemis still supports, together with its build plan management, result webhook and the Jenkins-specific user, profile and configuration handlingLocalCI (integrated build queue and build agents), combined with LocalVCDeprecated. Existing Jenkins installations keep working until Artemis 11.
MySQL as a supported database, including the MySQL JDBC driver, MySQL test and CI jobs, and the MySQL branches of the Liquibase baselinePostgreSQLDeprecated. Existing MySQL installations keep working until Artemis 11.

What this means in practice:

  • New installations should start with LocalCI and PostgreSQL. LocalVC stays: it is the version control system of both the Integrated Code Lifecycle and the Jenkins setup, and only Jenkins as a build system goes away.
  • Operators of Jenkins or MySQL installations should plan their migration during the 10.x releases, so that the upgrade to Artemis 11 is not combined with a change of build or database system.
  • The upgrade guide carries the operator-facing notice. The migration guides are Jenkins to LocalCI and MySQL to PostgreSQL.
  • The startup telemetry reports whether an installation runs Jenkins or MySQL.

Developers can find every place that goes away by searching the repository for the marker REMOVE_IN_ARTEMIS_11. Each marker names what is removed, (Jenkins) or (MySQL). The marker is placed on the declaration or configuration entry that owns the dependency, not on every use, so deleting the marked elements and then following the compiler, the architecture tests and the dead code checks finds the rest. When you add code that only exists for Jenkins or MySQL, add the marker as well.

As with every roadmap entry, the date is an intention and not a commitment.

Board items​

The board holds two kinds of item:

  • Larger features currently being implemented, linked to their pull requests. These carry the real status automatically, because the pull request is the item.
  • Strategic directions that are not yet implementation work, as drafts. A draft becomes a real issue as soon as someone picks it up, and from then on it is discussed, assigned, and closed like any other issue.

Smaller improvements and bug fixes are not on the roadmap. They go through the normal issue tracker and ship in the two-weekly releases.

Proposing something​

Anyone can propose something for the roadmap, whether or not they intend to build it:

  1. Open a feature request describing the problem, who has it, and why it matters. A problem is a better proposal than a solution.
  2. The maintainers evaluate it, and larger changes get a written feature proposal covering requirements, architecture, and UI/UX before any code is written.
  3. Accepted directions are added to the board.

Who keeps it current​

The maintainers review the board at their weekly meeting. That standing review is what keeps a roadmap alive; without it, boards quietly go stale and become misleading, which is worse than having none.

Search documentation