2022-11-27 13:04:43 -08:00
|
|
|
Releases
|
|
|
|
|
========
|
|
|
|
|
|
|
|
|
|
Versions
|
|
|
|
|
--------
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 1
|
|
|
|
|
|
2024-02-05 17:53:09 -08:00
|
|
|
0.11
|
2023-11-12 13:39:24 -08:00
|
|
|
0.10
|
2023-06-24 10:57:56 -07:00
|
|
|
0.9
|
2023-02-19 21:47:47 -08:00
|
|
|
0.8
|
2023-01-16 15:47:43 -08:00
|
|
|
0.7
|
2022-12-24 09:50:24 -08:00
|
|
|
0.6
|
2022-12-04 10:28:54 -08:00
|
|
|
0.5
|
2022-11-27 13:04:43 -08:00
|
|
|
0.4
|
|
|
|
|
0.3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Versioning Policy
|
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
|
|
Takahē approximately follows Semantic Versioning, with some specific
|
|
|
|
|
clarifications about what each upgrade means to you as a server administrator:
|
|
|
|
|
|
|
|
|
|
* **Patch** releases are bugfixes or small feature improvements that do not
|
|
|
|
|
require a database migration. It is safe to run patch versions from the same
|
|
|
|
|
minor series at the same time during an upgrade.
|
|
|
|
|
|
|
|
|
|
* **Minor** releases are larger feature improvements or other changes that
|
|
|
|
|
require a database migration. Unless otherwise noted, these will be
|
|
|
|
|
backwards-compatible migrations that can be applied to the database while the
|
|
|
|
|
previous version is still running, before the running code is updated.
|
|
|
|
|
|
|
|
|
|
* **Major** releases may have major breaking changes that require significant
|
|
|
|
|
upgrade time to perform, and will likely incur downtime. The exception will
|
|
|
|
|
be our 1.0 release, which will be treated as a minor release, continuing
|
|
|
|
|
on from the 0.x release series.
|
|
|
|
|
|
|
|
|
|
All release and upgrade notes can be found here, in the documentation.
|
