Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,059 of 9,059 pages
About the help in other languages
All help pages

The product lifecycle

The lifecycle view of Exponential for a public body - release policy, supported versions, PHP and platform support, the roadmap, upgrade budgets, security patching, a yearly rhythm and the end of a contract.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/procurement/lifecycle/README.md

On this page

The product lifecycle

This part of the procurement section is for project managers, contract managers and security officers in a public body who must plan an Exponential site over a contract of several years. It explains what a version number promises, which versions get fixes, how the platform under the software ages, and how to budget and contract for keeping the site current. The main sources are Source control and releases, SECURITY.md and Upgrading.

The pages

PageIt answers
Release policy and version numbersPublished versions never change; fixes come as the next release; where changes are recorded
Supported versions6.0.x is maintained; 5.x and older are not; how to require a supported version
PHP and platform supportPHP 8.0 to 8.5, six databases, the engines, and planning platform upgrades
Reading the roadmap as a public bodyThe roadmap is intent; the changelog is the record; how to request or fund a feature
Planning upgrades in the budgetThree kinds of upgrade, what drives the effort, a budget template
Security updates and patching cadenceFrom report to fix, what the project promises, a patching clause
Keeping a site current over a multi-year contractA monthly, quarterly and yearly rhythm with owners and a supplier report
The end of a contractRenew, re-tender or leave, and the handover each needs

Reading order

  1. Release policy and version numbers and Supported versions: what you can rely on.
  2. PHP and platform support: the layers below the software.
  3. Security updates and patching cadence and Planning upgrades in the budget: the obligations and their cost.
  4. Keeping a site current over a multi-year contract: the routine.
  5. Reading the roadmap as a public body and The end of a contract: the future, and the way out.

Key facts

  • A published tag is never changed; a fix reaches you as the next release (SECURITY.md).
  • 6.0.x is the maintained line; 5.x, 4.x, 3.x and older are not supported (SECURITY.md).
  • A private security report gets a first answer within one business day; no time to fix is promised (SECURITY.md).
  • PHP 8.0 to 8.5 are supported, Velocity included from its release 0.0.4.54 (2. Requirements).
  • The project publishes no SLA and no end-of-life dates (SLA options for Exponential hosting).

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x