Lines Matching full:version

14 The documentation for the current stable release version can always be found at this URL:
18 Documentation for the latest version (master branch) can always be found at this URL:
22 …u can find release notes, links to each version of the documentation, and instructions for obtaini…
26 …umentation page, where you can go to the upper-left corner and click the version dropdown (between…
37 Which Version Should I Start With?
40 …version`_. Stable versions have been manually tested, and are updated with "bugfix releases" which…
42 …ures, use the `latest version (master branch in Git) <https://docs.espressif.com/projects/esp-idf/…
44 …s possible to check out a pre-release version or a release branch. It is recommended to start from…
70 Each ESP-IDF major and minor release version has an associated support period. After this period, t…
79 …ew release is available. Whenever a bug fix release is available for the version you are using, pl…
80 - If possible, periodically update the project to a new major or minor ESP-IDF version (for example…
105 During the Maintenance period, the version is still supported but only bugfixes for high severity i…
107 Using an “In Service” version is recommended when starting a new project.
119 Checking the Current Version
122 The local ESP-IDF version can be checked by using idf.py::
124   idf.py --version
126 …version is also compiled into the firmware and can be accessed (as a string) via the macro ``IDF_V…
128 …ort multiple ESP-IDF versions, the version can be checked at compile time using :ref:`compile-time…
133 Version String               Meaning
136                              | - ``v3.2-dev`` - in development for version 3.2.
140 ``v3.1-beta1-75-g346d6b0ea`` | Beta version in development (on a :ref:`release branch <updating-rel…
154 - New work is always added on the master branch (latest version) first. The ESP-IDF version on ``ma…
156 - When a new version (developed on ``master``) becomes feature complete and "beta" quality, a new b…
157 - As testing of the beta version progresses, bug fixes will be added to both the ``master`` branch …
158 …ate is tagged on the release branch, for example ``v3.1-rc1``. This is still a pre-release version.
159 … found or reported, then the final Major or Minor Version is tagged, for example ``v3.1``. This ve…
169 Updating ESP-IDF depends on which version(s) you wish to follow:
175 …one, check Step 2 in the :doc:`Getting Started </get-started/index>` guide for any ESP-IDF version.
186 …ase for the version you are using is released (for example, if using ``v3.0.1`` and ``v3.0.2`` is …
202 Updating to a Pre-Release Version
205 It is also possible to ``git checkout`` a tag corresponding to a pre-release version or release can…
216 To use the latest version on the ESP-IDF master branch, this is the process to follow:
225 - Periodically, re-run ``git pull`` to pull the latest version of master. Note that you may need to…
226 - To switch from master to a release branch or stable version, run ``git checkout`` as shown in the…
228 …pportable "snapshots" that may have undocumented bugs. For a semi-stable version, try :ref:`updati…
249 …ase branches. It is recommended to use the documentation for the closest version to the branch whi…
254 .. _`current stable version`: https://docs.espressif.com/projects/esp-idf/en/stable/