Testing releases as a community member
Fixes and features are made on the main branch, "the 6.0.15 line, dev-main", and published with the next 6.0.x
release (SECURITY.md). Every community member who tries main on their own kind of setup before a release makes
that release better for everyone with the same setup.
Warning
Test only on a separate installation with invented data. Never on a production site, and never point an installer at a database you want to keep (Upgrading).
Contents
Set up a test installation
The simplest way is a Git clone of main installed on SQLite, which needs no database server:
- Clone the repository and note the commit you test (
git log -1 --format='%h %ad %s'). - Install it as Install in one command describes.
- Keep it current with Git (Develop with Git).
The detailed walk-through for advocates is Testing the development line.
What to test
| Area | How |
|---|---|
| Your everyday tasks | Edit, publish, upload, translate, build a page with layouts |
| What the changelog says is new | Follow the feature pages linked from the 6.0.15 changelog |
| Your setup | Your PHP version, database, engine (Velocity, Apache or nginx with PHP-FPM, FrankenPHP), operating system |
| Your extensions | The extensions your real sites use |
| Your language and accessibility needs | The administration in your language, with your assistive technology |
| An upgrade | A copy of a real site's structure with invented content, upgraded as Upgrading describes |
Describing a regression
"Worked in the last release, broken on main" is the most useful finding there is, because it points to a recent change. Name the commit:
Environment: Exponential main at <commit>, PHP <version>, <engine>, <database>, <design>
Worked in <last release>: <yes / no / unknown>
Steps: ...File it on the right tracker (Filing a bug).
Testing across many servers
Hosting companies and agencies often run many PHP versions, databases and operating systems. A test on each of them before a release is a contribution few others can make. Partners have a page of their own on this: Testing releases (partners). Requirements and supported combinations: Requirements, Database support, Operating system support.
Related pages
- Contributing as a community member
- Testing the development line
- Staying informed
- How releases happen
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
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.