Lines Matching full:releases
6 The Zephyr project releases on a time-based cycle, rather than a feature-driven
7 one. Zephyr releases represent an aggregation of the work of many contributors,
52 Information on previous releases can be found :ref:`here <zephyr_release_notes>`.
65 the release owner will declare that the development phase is over and releases the first
88 The mainline release owner releases new -rc drops once or twice a week; a normal
103 and participate in creating successful releases:
195 Releases section in Release Process
198 The following syntax should be used for releases and tags in Git:
217 :alt: Releases
221 Zephyr Code and Releases
228 Long-term support releases are designed to be supported and maintained
257 Zephyr LTS development cycle differs from regular releases and has an extended
258 stabilization period. Feature freeze of regular releases happens 3-4 weeks
269 went through the Zephyr API lifecycle and stabilized over at least 2 releases.
276 - All stable APIs need to be frozen 2 releases before an LTS. APIs can be extended
301 providing a quality oriented releases. This is achieved by providing the
373 - Supported by the Zephyr project itself, commitment to fix bugs in releases.
384 - Commitment to fix bugs in time for releases. Not supported by "Zephyr Project"
510 #. Find the new ``v1.11.0`` tag at the top of the releases page and
513 * Copy the overview of ``docs/releases/release-notes-1.11.rst``