Chapter 7. ESP-IDF Versions
If updating to a new major release (for example, from v2.1 to v3.0), some of your project’s code may
need updating and functionality may need to be re-tested. The release notes on the Releases page include lists
of Breaking Changes to refer to.
• Minor Releases like v3.1 add new functionality and fix bugs but will not change or remove documented
functionality, or make incompatible changes to public APIs.
If updating to a new minor release (for example, from v3.0 to v3.1), your project’s code does not require
updating, but you should re-test your project. Pay particular attention to the items mentioned in the release
notes on the Releases page.
• Bugfix Releases like v3.0.1 only fix bugs and do not add new functionality.
If updating to a new bugfix release (for example, from v3.0 to v3.0.1), you do not need to change any code
in your project, and you only need to re-test the functionality directly related to bugs listed in the release notes
on the Releases page.
7.4 Support Periods
Each ESP-IDF major and minor release version has an associated support period. After this period, the release is
End of Life and no longer supported.
The ESP-IDF Support Period Policy explains this in detail, and describes how the support periods for each release
are determined.
Each release on the Releases page includes information about the support period for that particular release.
As a general guideline:
• If starting a new project, use the latest stable release.
• If you have a GitHub account, click the “Watch”button in the top-right of the Releases page and choose
“Releases only”. GitHub will notify you whenever a new release is available. Whenever a bug fix release is
available for the version you are using, plan to update to it.
• If possible, periodically update the project to a new major or minor ESP-IDF version (for example, once a
year.) The update process should be straightforward for Minor updates, but may require some planning and
checking of the release notes for Major updates.
• Always plan to update to a newer release before the release you are using becomes End of Life.
Each ESP-IDF major and minor release (V4.1, V4.2, etc) is supported for 30 months after the initial stable release
date.
Supported means that the ESP-IDF team will continue to apply bug fixes, security fixes, etc to the release branch on
GitHub, and periodically make new bugfix releases as needed.
Support period is divided into “Service”and “Maintenance”period:
Period Duration Recommended for new projects?
Service 12 months Yes
Maintenance 18 months No
During the Service period, bugfixes releases are more frequent. In some cases, support for new features may be added
during the Service period (this is reserved for features which are needed to meet particular regulatory requirements
or standards for new products, and which carry a very low risk of introducing regressions.)
During the Maintenance period, the version is still supported but only bugfixes for high severity issues or security
issues will be applied.
Using an “In Service”version is recommended when starting a new project.
Users are encouraged to upgrade all projects to a newer ESP-IDF release before the support period finishes and the
release becomes End of Life (EOL). It is our policy to not continue fixing bugs in End of Life releases.
Pre-release versions (betas, previews, -rc and -dev versions, etc) are not covered by any support period. Sometimes a
particular feature is marked as “Preview”in a release, which means it is also not covered by the support period.
Espressif Systems 1588
Submit Document Feedback
Release v4.4
To Next Page
Loading...
Need help?
General