GITBOOK-9: Add lifecycle policy

This commit is contained in:
James Carppe
2024-11-30 07:37:15 +00:00
committed by gitbook-bot
parent eb526c5664
commit 91c14aec78
4 changed files with 98 additions and 3 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 45 KiB

View File

@@ -8,6 +8,7 @@
* [Introduction](start/intro.md)
* [Portainer architecture](start/architecture.md)
* [Lifecycle policy](start/lifecycle.md)
* [Requirements and prerequisites](start/requirements-and-prerequisites.md)
* [Install Portainer BE](start/install/README.md)
* [Set up a new Portainer BE Server installation](start/install/server/README.md)
@@ -321,7 +322,7 @@
* [Portainer Academy](https://academy.portainer.io)
* [YouTube](https://www.youtube.com/channel/UC7diMJcrULjDseq5yhSUZgg/videos)
* [GitHub](https://github.com/orgs/portainer/discussions)
* [Slack](https://join.slack.com/t/portainer/shared\_invite/zt-21zpww5ab-mG\_lA7UXbWL3HW3sPqjqEA)
* [Slack](https://join.slack.com/t/portainer/shared_invite/zt-21zpww5ab-mG_lA7UXbWL3HW3sPqjqEA)
* [Discord](https://discord.com/invite/j8fVken)
* [Open a support request](https://www.portainer.io/portainer-business-support)

View File

@@ -28,6 +28,6 @@ Portainer runs exclusively on your servers, within your network, behind your own
While we do (optionally) collect anonymous usage analytics from Portainer installations, we remain compliant with GDPR. Data collection can be disabled when you install the product, or at any time after that. If your installation is air-gapped, collection will silently fail without any adverse effects.
{% content-ref url="requirements-and-prerequisites.md" %}
[requirements-and-prerequisites.md](requirements-and-prerequisites.md)
{% content-ref url="lifecycle.md" %}
[lifecycle.md](lifecycle.md)
{% endcontent-ref %}

94
start/lifecycle.md Normal file
View File

@@ -0,0 +1,94 @@
# Lifecycle policy
Portainer makes this policy public so customers and partners can effectively plan, deploy, and support their container management infrastructure effectively using Portainer. It is published in an effort to provide as much transparency as possible but Portainer has the discretion to make exceptions from this policy should that be in Portainers or our customers best interests.
Any release dates are provided for guidance only and the exact dates may change.
## The Portainer lifecycle <a href="#the-portainer-lifecycle" id="the-portainer-lifecycle"></a>
Portainer releases approximately follow a monthly cadence for minor releases (X.Y) which can introduce feature enhancements and new features but endeavor to maintain backward compatibility.
Micro or patch releases (X.Y.z) are released as needed and are limited to backward compatible bug fixes only.
Major versions (X) will be much less frequent, will include potential breaking changes, and may require an upgrade or migration process from previous versions.
All releases are cumulative - all previous enhancements and fixes are included in each release.
## Terminology <a href="#terminology" id="terminology"></a>
### Supported versus maintained <a href="#supported-versus-maintained" id="supported-versus-maintained"></a>
When we say “supported”, we are referring to the commercial support that is included with Portainer Business Edition subscriptions at the Scale and Enterprise level. This includes access to all STS and LTS releases and patches. Our [support terms](https://www.portainer.io/support-terms) have more detail on what is and isnt covered by our support.
For Starter, Home & Student, our free Business Edition offerings, and our Community Edition, support is provided through our [community support channels](https://www.portainer.io/get-support-for-portainer).
The term “maintained” refers to the act of releasing updated versions of our releases, for example patches to resolve bugs or security issues. All editions of Business Edition and Community Edition will be maintained according to each releases respective lifecycle.
Portainer always recommends updating to the latest version in the release stream to ensure you have the latest security fixes, bug fixes, and performance improvements. It is at Portainers discretion to backport fixes to any version outside of the supported version window.
### STS versus LTS <a href="#sts-versus-lts" id="sts-versus-lts"></a>
Portainer has two release streams, STS and LTS and its important you know the differences so you can choose accordingly.
#### **Short Term Support (STS) releases**
Short Term Support releases are identified with an “STS” suffix.
These are supported and maintained until the release of the next STS or LTS version. Use STS versions if you are interested in getting the latest features faster and dont mind upgrading more frequently.
#### **Long Term Support (LTS) releases**
Long Term Support releases are identified with an “LTS” suffix.
These releases are supported and maintained until the release of the next LTS version plus a three month migration window so are more suitable for environments where adding new features on a frequent basis is less desirable.
{% hint style="info" %}
Portainer LTS releases focus less on new features and more on stability so Portainer recommends LTS releases for production workloads.
{% endhint %}
## Current and planned releases
Each stream (LTS and STS) will have a number of patch releases throughout its life.
### Current releases
| Release | Release Date | End of support/maintenance |
| ------------ | ------------ | -------------------------- |
| **2.21 LTS** | **Aug 2024** | **Jul 2025** |
| 2.24 STS | Nov 2024 | Dec 2024 |
### Planned releases
| Release | Release Date | End of support/maintenance |
| ------------ | ------------ | -------------------------- |
| 2.25 STS | Dec 2024 | Jan 2025 |
| 2.26 STS | Jan 2025 | Feb 2025 |
| **2.27 LTS** | **Feb 2025** | **Nov 2025** |
<figure><img src="../.gitbook/assets/portainer-lifecycle-releases.png" alt=""><figcaption></figcaption></figure>
Sitting on an older release that is no longer maintained or supported is strongly discouraged and customers take full responsibility for doing so. Customers are strongly encouraged to ensure they are running the latest patch release for a given stream.
## Older releases that are no longer supported or maintained
The following releases have passed the end of support date and are no longer maintained or supported. If you are using one of these versions (or older), we recommend that you [update](upgrade/) as soon as possible.
| Release | Release Date | End of support/maintenance |
| -------- | ------------ | -------------------------- |
| 2.17 | Feb 2023 | Apr 2023 |
| 2.18 | Apr 2023 | Aug 2023 |
| 2.19 | Aug 2023 | Aug 2024 |
| 2.20 STS | Mar 2024 | Aug 2024 |
| 2.22 STS | Sep 2024 | Oct 2024 |
| 2.23 STS | Oct 2024 | Nov 2024 |
## Notes
Portainer uses the [semantic versioning scheme](https://semver.org/) and while Portainer endeavors to follow best practices, we reserve the right to make exceptions should that be in Portainers and our customers best interests.
For information on the available options and best practices for updating Portainer deployments, [refer to our update documentation](upgrade/).
{% content-ref url="requirements-and-prerequisites.md" %}
[requirements-and-prerequisites.md](requirements-and-prerequisites.md)
{% endcontent-ref %}