Git Workflow; Updating Esp-Idf - Espressif ESP32-S2 Programming Manual

Chapter 7. ESP-IDF Versions
Version String
v3.2-dev-306-gbeb3611ca
v3.0.2
v3.1-beta1-75-g346d6b0ea
v3.0.1-dirty
7.6 Git Workflow
The development (Git) workflow of the Espressif ESP-IDF team is as follows:
• New work is always added on the master branch (latest version) first. The ESP-IDF version on master is
always tagged with -dev (for "in development"), for example v3.1-dev.
• Changes are first added to an internal Git repository for code review and testing but are pushed to GitHub after
automated testing passes.
• When a new version (developed on master) becomes feature complete and "beta"quality, a new branch
is made for the release, for example release/v3.1. A pre-release tag is also created, for example v3.1-
beta1. You can see a full
which may include a significant number of Known Issues.
• As testing of the beta version progresses, bug fixes will be added to both the master branch and the release
branch. New features for the next release may start being added to master at the same time.
• Once testing is nearly complete a new release candidate is tagged on the release branch, for example v3.1-
rc1. This is still a pre-release version.
• If no more significant bugs are found or reported, then the final Major or Minor Version is tagged, for example
v3.1. This version appears on the
• As bugs are reported in released versions, the fixes will continue to be committed to the same release branch.
• Regular bugfix releases are made from the same release branch. After manual testing is complete, a bugfix
release is tagged (i.e. v3.1.1) and appears on the

7.7 Updating ESP-IDF

Updating ESP-IDF depends on which version(s) you wish to follow:
• Updating to Stable Release
Espressif Systems
Meaning
Master branch pre-release.
- v3.2-dev - in development for version 3.2.
- 306 - number of commits after v3.2 development
started.
- beb3611ca - commit identifier.
Stable release, tagged v3.0.2.
Beta version in development (on a
- v3.1-beta1 - pre-release tag.
- 75 - number of commits after the pre-release beta
tag was assigned.
- 346d6b0ea - commit identifier.
Stable release, tagged v3.0.1.
- dirty means that there are modifications in the
local ESP-IDF directory.
list of branches and a list of tags
Releases page.
Releases
is recommended for production use.
1590
Submit Document Feedback
on GitHub. Beta pre-releases have release notes
page.
release branch).
Release v4.4