Lines Matching refs:new
6 The ESP-IDF GitHub repository is updated regularly, especially the master branch where new developm…
42 - For prototyping, experimentation or for developing new ESP-IDF features, use the `latest version …
55 - Major Releases, like ``v3.0``, add new functionality and may change functionality. This includes …
57 …If updating to a new major release (for example, from ``v2.1`` to ``v3.0``), some of your project'…
59 - Minor Releases like ``v3.1`` add new functionality and fix bugs but will not change or remove doc…
61 …If updating to a new minor release (for example, from ``v3.0`` to ``v3.1``), your project's code d…
63 - Bugfix Releases like ``v3.0.1`` only fix bugs and do not add new functionality.
65 …If updating to a new bugfix release (for example, from ``v3.0`` to ``v3.0.1``), you do not need to…
78 - If starting a new project, use the latest stable release.
79 …eases page`_ and choose "Releases only". GitHub will notify you whenever a new release is availabl…
80 - If possible, periodically update the project to a new major or minor ESP-IDF version (for example…
85 …security fixes, etc to the release branch on GitHub, and periodically make new bugfix releases as …
95 - Recommended for new projects?
103 …new features may be added during the Service period (this is reserved for features which are neede…
107 Using an “In Service” version is recommended when starting a new project.
156 - When a new version (developed on ``master``) becomes feature complete and "beta" quality, a new b…
158 - Once testing is nearly complete a new release candidate is tagged on the release branch, for exam…
183 To update to a new ESP-IDF release (recommended for production use), this is the process to follow:
185 - Check the `Releases page`_ regularly for new releases.
186 …or example, if using ``v3.0.1`` and ``v3.0.2`` is released), check out the new bugfix version into…
197 … update versions using the commands. In this case, update by downloading a new zip file and replac…