| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 3 Release Process
10 A time-based release process enables the Zephyr project to provide users with a
12 roughly 4-month release cycle allows the project to coordinate development of
14 maintain the quality of the overall release without delays because of one or two
17 The Zephyr release model was loosely based on the Linux kernel model:
19 - Release tagging procedure:
22 - release branches for maintenance after release tagging.
23 - Each release period will consist of a development phase followed by a
24 stabilization phase. Release candidates will be tagged during the
31 - Stabilisation phase: the release manager creates a vN-rc1 tag and the tree
[all …]
|
| D | proposals.rst | 11 block a release. This is an incremental enhancement to a feature that already
16 that is not part of any release plans yet, that has not been vetted, and needs
38 willingness to drive implementation of the feature in an upcoming release, and
63 Roadmap and Release Plans
66 Project roadmaps and release plans are both important tools for the project, but
68 communicates the high-level overview of a project's strategy, while a release
72 - The project roadmap communicates the why; a release plan details the what
73 - A release plan spans only a few months; a product roadmap might cover a year
93 Release Plans
96 The release plan comes into play when the project roadmap's high-level strategy
[all …]
|
| D | project_roles.rst | 93 * Responsibility to participate in the quality verification and release
147 Release Engineering Team member, Release Manager, but are no longer engaged
166 by the other Maintainers, the Release Engineering team can set an assignee when
183 The Static Analysis Audit team works closely with the release engineering
184 team to ensure that static analysis defects opened during a release
202 Release Engineering Team
207 * The members of the Release Engineering team are expected to fill
208 the Release Manager role based on a defined cadence and selection process.
209 * The cadence and selection process are defined by the Release Engineering
213 Release Engineering team has the following rights and responsibilities:
[all …]
|
| /Zephyr-latest/.github/workflows/ |
| D | release.yml | 1 name: Create a Release
10 release:
35 - name: Create empty release notes body
37 echo "TODO: add release overview and notes link" > release-notes.txt
39 - name: Create Release
41 uses: actions/create-release@v1
47 body_path: release-notes.txt
51 - name: Upload Release Assets
52 id: upload-release-asset
53 uses: actions/upload-release-asset@v1
|
| /Zephyr-latest/doc/releases/ |
| D | eol_releases.rst | 6 Release notes and migration guides for end-of-life releases of Zephyr RTOS are kept here for
11 Release Notes
19 release-notes-1.?
20 release-notes-1.*
21 release-notes-2.[0-6]
22 release-notes-3.[0-6]
|
| D | index.rst | 12 :ref:`west` to :ref:`get_the_code` of the release you are interested in.
15 https://docs.zephyrproject.org/ (use the version selector to select your release
20 Release Life Cycle and Maintenance
35 A Zephyr :ref:`Long Term Support (LTS) <release_process_lts>` release is
39 Support and maintenance for an LTS release stops at least half a year
40 after the following LTS release is published.
48 - Currently supported Long Term Support (LTS) release.
59 | Release | Release date | EOL |
70 Release Notes
73 Release notes contain a list of changes that have been made to the different
[all …]
|
| /Zephyr-latest/.github/ |
| D | SECURITY.md | 8 - The most recent release, and the release prior to that.
11 At this time, with the latest release of v4.0, the supported
14 - v4.0: Current release
16 - v3.6: Prior release
|
| /Zephyr-latest/include/zephyr/arch/arc/v2/vpx/ |
| D | arc_vpx.h | 31 * @brief Release cooperative lock on the VPX vector registers
33 * This function is used to release the cooperative lock on the current CPU's
42 * @brief Release cooperative lock on a CPU's VPX vector registers
44 * This function is used to release the cooperative lock on the specified CPU's
46 * monitor to release the cooperative lock in case the locking thread where it
47 * is known that the locking thread is unable to release it (e.g. it was
|
| /Zephyr-latest/dts/bindings/input/ |
| D | zephyr,input-longpress.yaml | 30 # release before one second
31 input event: dev=buttons SYN type= 1 code= 11 value=0 # INPUT_KEY_0 release
33 input event: dev=longpress SYN type= 1 code= 30 value=0 # INPUT_KEY_A release
39 # wait for release
40 input event: dev=buttons SYN type= 1 code= 11 value=0 # INPUT_KEY_0 release
41 input event: dev=longpress SYN type= 1 code= 45 value=0 # INPUT_KEY_X release
|
| /Zephyr-latest/samples/boards/nordic/nrf_sys_event/src/ |
| D | main.c | 25 printf("release global constant latency mode\n"); in main()
28 printf("failed to release global constant latency mode\n"); in main()
32 printf("release global constant latency mode again\n"); in main()
35 printf("failed to release global constant latency mode\n"); in main()
|
| /Zephyr-latest/tests/subsys/portability/cmsis_rtos_v2/src/ |
| D | semaphore.c | 24 /* Try taking semaphore after a TIMEOUT, but before release */ in thread_sema()
35 * and release it. in thread_sema()
41 "Semaphore release failure"); in thread_sema()
101 /* Release invalid semaphore */ in ZTEST()
103 "Semaphore release worked unexpectedly"); in ZTEST()
105 /* Release the semaphore to be used by the other thread */ in ZTEST()
107 zassert_true(status == osOK, "Semaphore release failure"); in ZTEST()
|
| D | mutex.c | 71 /* Try to release mutex without obtaining it */ in ZTEST()
92 zassert_true(status == osOK, "Mutex release failure"); in ZTEST()
94 /* Release mutex again as it was acquired twice */ in ZTEST()
96 zassert_true(status == osOK, "Mutex release failure"); in ZTEST()
98 /* Try to release mutex that was already released */ in ZTEST()
136 * and release it. in tThread_entry_lock_timeout()
174 /* Release the mutex to be used by the other thread */ in ZTEST()
|
| /Zephyr-latest/samples/boards/st/power_mgmt/blinky/src/ |
| D | main.c | 35 /* Release resource to release device clock */ in main()
40 /* Release resource to release device clock */ in main()
|
| /Zephyr-latest/tests/subsys/portability/cmsis_rtos_v1/src/ |
| D | mutex.c | 62 /* Try to release mutex without obtaining it */ in ZTEST()
74 zassert_true(status == osOK, "Mutex release failure"); in ZTEST()
76 /* Release mutex again as it was acquired twice */ in ZTEST()
78 zassert_true(status == osOK, "Mutex release failure"); in ZTEST()
80 /* Try to release mutex that was already released */ in ZTEST()
105 * Trying to release it here should fail. in tThread_entry_lock_timeout()
116 * and release it. in tThread_entry_lock_timeout()
143 /* Release the mutex to be used by the other thread */ in ZTEST()
|
| D | semaphore.c | 24 /* Try taking semaphore after a TIMEOUT, but before release */ in thread_sema()
35 * and release it. in thread_sema()
41 "Semaphore release failure"); in thread_sema()
68 /* Release the semaphore to be used by the other thread */ in ZTEST()
70 zassert_true(status == osOK, "Semaphore release failure"); in ZTEST()
|
| /Zephyr-latest/samples/posix/uname/src/ |
| D | main.c | 19 printf("release[%zu]: %s\n", sizeof(info.release), info.release); in main()
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 91 - The Zephyr release owners for the relevant releases affected by
133 Each Zephyr release shall contain a report of CVEs that were fixed in
134 that release. Because of the sensitive nature of these
135 vulnerabilities, the release shall merely include a list of CVEs that
180 - The current Long Term Stable (LTS) release.
185 backports, and apply them to any of the above listed release branches,
187 this release was made). All recommendations for
191 release manager that the backport pull request and issue are addressing
207 - The current release manager, and the release manager for historical
215 - As needed, release managers and maintainers may be invited to attend
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/classic/ |
| D | a2dp.rst | 18 * Source or Sink release the media. using :code:`a2dp release`.
66 uart:~$ a2dp release
67 success to release
99 <after a2dp release of source side>
100 receive requesting release and accept
|
| /Zephyr-latest/soc/st/stm32/stm32wbx/ |
| D | power.c | 47 /* Release ENTRY_STOP_MODE semaphore */ in lpm_hsem_lock()
83 /* Release RCC semaphore */ in pm_state_set()
91 * Release CLK48 semaphore to make sure M0 core can enable/disable in pm_state_set()
100 /* Release RCC semaphore */ in pm_state_set()
117 /* Release ENTRY_STOP_MODE semaphore */ in pm_state_exit_post_ops()
142 /* Release RCC semaphore */ in pm_state_exit_post_ops()
|
| /Zephyr-latest/include/zephyr/ |
| D | kernel_version.h | 26 * x -- major release
27 * y -- minor release
28 * z -- patchlevel release
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 185 - An entry in the "API Changes" section of the release notes for the next
186 upcoming release
187 - The labels ``API``, ``Breaking API Change`` and ``Release Notes``, as well as
216 section of the release notes.
222 For example, if an API was first deprecated in release 4.0,
234 - Include the deprecation in the "API Changes" of the release notes for the
235 next upcoming release
239 - Add an entry in the corresponding release
242 In this example in the one corresponding to the 4.2 release.
266 the release notes, mailing lists, Github issues and pull-requests.
[all …]
|
| /Zephyr-latest/tests/drivers/clock_control/onoff/src/ |
| D | test_clock_control_onoff.c | 74 /* Attempt to release while ongoing start. Cannot do that */ in ZTEST()
92 /* Test checks if premature clock release works ok. If clock is released before
93 * it is started it is the best to do that release from the callback to avoid
94 * waiting until clock is started in the release context.
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | csip.rst | 13 or a laptop. The client is able to lock and release members of a coordinated
37 all the members has been connected to, it can lock and release the set.
52 release_set :Release set
54 release :Release specific member [member_index]
124 Release set members:
151 release :Release the set [force]
|
| /Zephyr-latest/subsys/bluetooth/controller/ll_sw/ |
| D | ull_df_internal.h | 10 /* Release link to node_rx_iq_report memory. */
12 /* Release memory of node_rx_iq_report. */
|
| /Zephyr-latest/tests/bluetooth/controller/ctrl_phy_update/src/ |
| D | main.c | 151 /* Make sure we use a correct type or the release won't work */ in ZTEST()
177 /* Release Tx */ in ZTEST()
189 /* Release RX node to now allow pre-alloc for DLE NTF */ in ZTEST()
212 /* Release Tx */ in ZTEST()
243 /* Release Ntf */ in ZTEST()
247 /* Release Ntf */ in ZTEST()
300 /* Release Tx */ in ZTEST()
357 /* Release Tx */ in ZTEST()
370 /* Release Ntf */ in ZTEST()
399 /* Make sure we use a correct type or the release won't work */ in ZTEST()
[all …]
|
