Home
last modified time | relevance | path

Searched refs:release (Results 1 – 25 of 292) sorted by relevance

12345678910>>...12

/Zephyr-latest/.github/
DSECURITY.md8 - 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.1: Current release
15 - v4.0: Prior release
/Zephyr-latest/doc/releases/
Deol_releases.rst19 release-notes-1.?
20 release-notes-1.*
21 release-notes-2.[0-6]
22 release-notes-3.[0-6]
Dindex.rst12 :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
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.
83 areas of the project during the development cycle of the release.
85 release may be mentioned in the release notes, but the details regarding *what*
86 needs to be changed are to be detailed in the release's migration guide.
88 Updates to the release notes post release cycle is permitted but limited to
[all …]
Drelease-notes-4.2.rst7 is worth mentioning in the project media (release blog post, release
11 actual project documentation rather than the release notes, so that the
32 We are pleased to announce the release of Zephyr version 4.2.0.
34 Major enhancements with this release include:
43 The following CVEs are addressed by this release:
113 You may update this list as you contribute a new board during the release cycle, in order to make
114 it visible to people who might be looking at the working draft of the release notes. However, note
115 that this list will be recomputed at the time of the release, so you don't *have* to update it.
122 Same as above for boards, this will also be recomputed at the time of the release.
129 Same as above for boards and drivers, this will also be recomputed at the time of the release.
Drelease-notes-1.5.rst6 The Zephyr Engineering team is glad to announce the release of Zephyr Kernel
7 1.5.0. This is the first release to follow the 3-month release cadence.
8 This release includes numerous fixes and support for major features.
11 Major enhancements included with the release:
269 - No workaround, will fix in future release.
275 - No workaround, will fix in future release.
278 - No workaround, will fix in future release.
281 - No workaround, will fix in future release.
284 - No workaround, will fix in future release.
287 - No workaround, will fix in future release.
/Zephyr-latest/doc/project/
Drelease_process.rst10 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:
22 - release branches for maintenance after release tagging.
23 - Each release period will consist of a development phase followed by a
31 - Stabilisation phase: the release manager creates a vN-rc1 tag and the tree
35 - The release owner, with test teams and any other needed input, determines if the
36 release candidate is a go for release
37 - If it is a go for a release, the release owner lays a tag release vN at the
[all …]
Dproposals.rst11 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
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
96 The release plan comes into play when the project roadmap's high-level strategy
98 and fixes that need to go into a specific release or milestone.
100 The release plan communicates those features and enhancements slated for your
[all …]
/Zephyr-latest/samples/posix/uname/src/
Dmain.c19 printf("release[%zu]: %s\n", sizeof(info.release), info.release); in main()
/Zephyr-latest/doc/connectivity/bluetooth/shell/classic/
Da2dp.rst18 * 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/lib/posix/options/
Duname.c33 .sysname = _sys, .nodename = _node, .release = _rel, \
41 BUILD_ASSERT(sizeof(z_name.release) >= sizeof(KERNEL_VERSION_STRING));
/Zephyr-latest/tests/bluetooth/audio/cap_initiator/src/
Dtest_unicast_stop.c118 .release = false, in ZTEST_F()
153 .release = false, in ZTEST_F()
187 .release = false, in ZTEST_F()
221 .release = false, in ZTEST_F()
256 .release = true, in ZTEST_F()
291 .release = true, in ZTEST_F()
325 .release = true, in ZTEST_F()
359 .release = true, in ZTEST_F()
404 .release = true, in ZTEST_F()
422 .release = true, in ZTEST_F()
[all …]
/Zephyr-latest/doc/security/
Dreporting.rst91 - 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/include/zephyr/posix/sys/
Dutsname.h24 char release[sizeof("99.99.99-rc1")]; member
/Zephyr-latest/scripts/west_commands/
Dsdk.py256 def minimal_sdk_filename(self, release): argument
258 version = re.sub(r"^v", "", release["tag_name"])
273 def minimal_sdk_sha256(self, sha256_list, release): argument
274 name = self.minimal_sdk_filename(release)
280 def minimal_sdk_url(self, release): argument
281 name = self.minimal_sdk_filename(release)
282 assets = release.get("assets", [])
287 def sha256_sum_url(self, release): argument
288 assets = release.get("assets", [])
/Zephyr-latest/boards/arm/fvp_base_revc_2xaemv8a/
Dboard.cmake42 set(FVP_SECURE_FLASH_FILE ${TFA_BINARY_DIR}/fvp/release/bl1.bin)
43 set(FVP_FLASH_FILE ${TFA_BINARY_DIR}/fvp/release/fip.bin)
/Zephyr-latest/include/zephyr/drivers/
Dmipi_dbi.h166 int (*release)(const struct device *dev, member
317 if (api->release == NULL) { in mipi_dbi_release()
320 return api->release(dev, config); in mipi_dbi_release()
/Zephyr-latest/subsys/shell/backends/
Dshell_rpmsg.c137 bool release = true; in read() local
160 release = false; in read()
166 if (release) { in read()
/Zephyr-latest/include/zephyr/drivers/clock_control/
Dnrf_clock_control.h195 int (*release)(const struct device *dev, member
284 return api->release(dev, spec); in nrf_clock_control_release()
/Zephyr-latest/drivers/spi/
Dspi_grlib_spimctrl.c152 static int release(const struct device *dev, const struct spi_config *config) in release() function
226 .release = release,
Dspi_test.c52 .release = vnd_spi_release,
/Zephyr-latest/drivers/flash/
Dflash_mspi_emul_device.c82 static void release(const struct device *flash) in release() function
184 release(flash); in flash_mspi_emul_erase()
253 release(flash); in flash_mspi_emul_write()
304 release(flash); in flash_mspi_emul_read()
405 release(emul_flash->dev); in emul_mspi_device_init()
Dspi_flash_at45.c100 static void release(const struct device *dev) in release() function
280 release(dev); in spi_flash_at45_read()
370 release(dev); in spi_flash_at45_write()
513 release(dev); in spi_flash_at45_erase()
607 release(dev); in spi_flash_at45_init()
622 release(dev); in spi_flash_at45_pm_action()
630 release(dev); in spi_flash_at45_pm_action()
/Zephyr-latest/samples/boards/st/power_mgmt/standby_shutdown/
DREADME.rst16 release the user button to exit from shutdown mode or from shutdown mode.
43 release the user button to exit from shutdown mode or from shutdown mode.
/Zephyr-latest/subsys/fs/
Dfuse_fs_access_bottom.h32 int (*release)(uint64_t fh); member
/Zephyr-latest/scripts/
Drequirements-extras.txt21 # used by scripts/release/bug_bash.py for generating top ten bug squashers

12345678910>>...12