| /Zephyr-Core-3.6.0/doc/project/ |
| D | code_flow.rst | 18 shall be based off the main branch and any changes developed in the collab
32 Changes submitted to a collaboration branch can evolve and improve
44 * Define exit criteria for merging the collaboration branch changes back into the main branch.
55 - All changes to collaboration branches shall come in form of github pull requests.
57 - Review changes coming from team members and request review from branch owners
58 when submitting changes.
60 - Push changes frequently to upstream using the following methods:
64 - Merge requests: When a set of changes has been done in a local branch and
|
| D | dev_env_and_tools.rst | 10 is accepted into the code base. Changes, in the form of Pull Requests (PR) are
36 changes are proposed using pull request, we need to allow for a minimal review
38 on changes. There are different categories of changes and we know that some
39 changes do require reviews by subject matter experts and owners of the subsystem
40 being changed. Many changes fall under the "trivial" category that can be
42 code-owner review. Additionally, some changes might require further discussions
59 changes can change the label of a pull request by adding a comment justifying
62 - Changes should not be merged before the minimal time has expired.
82 Trivial changes are those that appear obvious enough and do not require maintainer or code-owner
83 involvement. Such changes should not change the logic or the design of a
[all …]
|
| D | project_roles.rst | 72 and requested changes should still be considered by the pull request author.
87 * Responsibility to review relevant code changes within reasonable time.
99 be addressed by the original submitter. In cases where the changes requested do
165 * Right to block pull requests from being merged until issues or changes
208 * Right to merge code changes to the zephyr tree following the project rules.
209 * Right to revert any changes that have broken the code base
210 * Right to close any stale changes after <N> months of no activity
255 verify changes either directly or through QA before major
256 changes and major milestones.
309 in a standalone commit alongside other changes introducing new files and
[all …]
|
| D | issues.rst | 6 To maintain traceability and relation between proposals, changes, features, and
9 Any changes that originate from a tracked feature or issue should contain a
|
| D | release_process.rst | 26 changes such as bug fixes and documentation will be merged unless granted a
29 - Development phase: all changes are considered and merged, subject to
61 merged into the mainline tree. The bulk of changes for a new development cycle
62 (and all of the major changes) will be merged during this time.
144 - No new features, ONLY stabilization and cosmetic changes, bug and doc fixes are allowed.
148 - No new features, ONLY stabilization and cosmetic changes, bug and doc fixes are allowed.
152 - Only blocker bug fixes, documentation and changes to release notes are allowed.
308 Changes and fixes flow in both directions. However, changes from main branch to an
|
| /Zephyr-Core-3.6.0/doc/develop/api/ |
| D | api_lifecycle.rst | 58 Changes will not be announced.
76 minor changes. Backwards-compatibility will be maintained if reasonable.
89 #. A Pull Request must be opened that changes the corresponding entry in the
99 Introducing breaking API changes
127 - Function call changes
128 - Device Tree changes (source and bindings)
129 - Kconfig option changes
134 Instead of a written description of the changes, the RFC issue may link to a
135 Pull Request containing those changes in code form.
155 - The actual changes to the API
[all …]
|
| /Zephyr-Core-3.6.0/subsys/bluetooth/audio/ |
| D | Kconfig.pacs | 20 PAC Characteristic changes.
40 Audio Location Characteristic changes.
55 PAC Characteristic changes.
75 Audio Location Characteristic changes.
87 Supported Audio Contexts Characteristic changes.
|
| /Zephyr-Core-3.6.0/doc/contribute/ |
| D | contributor_expectations.rst | 7 changes as smaller pull requests. Smaller pull requests (PRs) have the following
11 to set aside a few minutes to review smaller changes several times than it is
18 changes in the tree.
42 - Modifying a feature, especially for API behavior contract changes.
62 the PR into multiple commits targeting these specific changes:
71 Large Changes
74 Large changes to the Zephyr project must submit an :ref:`RFC proposal <rfcs>`
80 Changes which require an RFC proposal include:
84 - :ref:`treewide-changes`.
85 - Other large changes that can benefit from the RFC proposal process.
[all …]
|
| D | proposals_and_rfcs.rst | 6 Many changes, including bug fixes and documentation improvements can be
9 Many changes however are "substantial" and need to go through a
16 they intend to make "substantial" changes to Zephyr or its documentation. Some
24 include code changes to Zephyr itself.
36 Some changes do not require an RFC:
|
| D | guidelines.rst | 8 standards and methods for submitting changes help reduce the chaos that can result
160 - If you've pushed your changes to GitHub already you'll need to force push
322 similar ideas for changes or additions. Send a message to the `Zephyr devel
384 To verify that your changes did not break any tests or samples, please run the
415 In case of major changes to the kernel, build or configuration infrastructures
416 of Zephyr, it is advised to use twister for verifying majority the changes
569 controlled changes. This practice simplifies review, makes merging and
574 and test your changes thoroughly before submitting.
625 #. Make changes, test locally, change, test, test again, ... (Check out the
637 #. Verify changes to be committed look as you expected::
[all …]
|
| /Zephyr-Core-3.6.0/scripts/checkpatch/ |
| D | timestamp | 14 # where: -a changes default to: 2015-01-14-18-11-56
15 # -d changes default to: 20150114
16 # -u changes default to: 20150114_181201
17 # -s changes default to: 20150114-1812.04
18 # -S changes default to: 20150114-1812
|
| /Zephyr-Core-3.6.0/scripts/release/ |
| D | list_devicetree_bindings_changes.py | 18 # TODO: include changes to child bindings
43 below for concrete changes.
50 class Changes: class
51 '''Container for all the changes that happened between the
117 ) -> Changes:
141 return Changes(vnds=sorted(vnds_set),
165 for binding, changes in binding2changes.items():
166 ret[get_vnd(binding.compatible)][binding] = changes
201 '''Enumerate the changes to a binding given its start and end values.'''
408 def print_changes(self, changes: Changes): argument
[all …]
|
| /Zephyr-Core-3.6.0/subsys/fs/ext2/ |
| D | ext2_diskops.h | 110 * @brief Commit changes made to inode structure
112 * The changes are committed only to the cached block. They are truly written to
123 * @brief Commit changes made to inode block
125 * The changes are committed only to the cached block. They are truly written to
136 * @brief Commit changes made to superblock structure.
138 * The changes made to program structure are copied to disk representation and written to the
149 * @brief Commit changes made to block group structure.
151 * The changes made to program structure are copied to disk representation and written to the
|
| /Zephyr-Core-3.6.0/doc/develop/west/ |
| D | release-notes.rst | 9 Major changes:
46 Other changes:
61 API changes:
84 Major changes:
99 Other changes:
114 API changes:
122 Major changes:
139 Major changes in this release:
141 - The :ref:`west-apis` are now declared stable. Any breaking changes will be
157 Other changes:
[all …]
|
| /Zephyr-Core-3.6.0/doc/releases/ |
| D | index.rst | 71 Release notes contain a list of changes that have been made to the different
73 Changes that require the user to modify their own application to support the new
92 As mentioned in the previous section, changes in the code that require an action
97 - Breaking API changes
99 - Devicetree or Kconfig changes that affect the user (changes to defaults,
101 - Treewide changes that have an effect (e.g. changing the include path or
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg.rst | 14 local constraints, such as low battery power or changes in topology. For these
18 Runtime configuration changes before the node is provisioned will not be stored
|
| /Zephyr-Core-3.6.0/doc/develop/ |
| D | modules.rst | 122 Changes to the main branch of a module repository, including synchronization
126 ensures that the incoming changes are always **reviewable**, and the
130 changes that are to be brought into the module repository.
146 Upstream changes brought as a single *snapshot* commit (manual diff) in a
162 Upstream changes brought in by performing a Git merge of the intended upstream
229 * the contributor of the original changes in Zephyr is required to submit
230 the corresponding changes that are required in module repositories, to
231 ensure that Zephyr CI on the pull request with the original changes, as
244 Contributing changes to modules
247 Submitting and merging changes directly to a module's codebase, that is,
[all …]
|
| /Zephyr-Core-3.6.0/include/zephyr/drivers/uart/ |
| D | cdc_acm.h | 25 * @brief A function that is called when the USB host changes the baud
37 * The callback is invoked when the USB host changes the baud rate.
|
| /Zephyr-Core-3.6.0/subsys/net/lib/lwm2m/ |
| D | README_lwm2m | 23 …attempt to use the 3-way merge capabilities by committing the un-patched changes (i.e. up to and i…
29 The patch was created by, committing the unpatched changes, then committing the desired patches in …
|
| /Zephyr-Core-3.6.0/subsys/usb/device/class/ |
| D | Kconfig.cdc | 56 bool "Support callbacks when the USB host changes the virtual baud rate"
60 remote host changes the virtual baud rate. This is used
|
| /Zephyr-Core-3.6.0/doc/build/snippets/ |
| D | design.rst | 26 - **future-proof and backwards-compatible**: arbitrary future changes to the
30 - **applicable to purely "software" changes**: unlike the shields feature,
|
| /Zephyr-Core-3.6.0/doc/services/tfm/ |
| D | testsuites.rst | 41 changes to TF-M, such as enabling a new TF-M board target, or making changes
|
| /Zephyr-Core-3.6.0/samples/application_development/sysbuild/with_mcuboot/sysbuild/ |
| D | mcuboot.conf | 1 # Example of sample specific Kconfig changes when building sample with MCUboot
|
| /Zephyr-Core-3.6.0/doc/safety/ |
| D | safety_overview.rst | 29 #. Changes will be submitted from the interested party(ies) via pull requests to the Zephyr
32 #. The Zephyr Safety Committee will review these changes and provide feedback or acceptance of
33 the changes.
35 #. Once accepted, these changes will become part of the document.
152 faulty changes and further minimizing the error rate. However, it must be noted that different
228 and decisions of minor changes in the safety scope to be able to react to safety-relevant
229 changes that are not conformant. If a pull request or issue introduces a significant and
236 "auditable" state, and ideally no further changes should be necessary or made to the code base.
255 a path to merge these changes back into the main branch so that they are not lost, and to have
|
| /Zephyr-Core-3.6.0/drivers/eeprom/ |
| D | Kconfig.eeprom_emu | 13 larger than the EEPROM area and by storing only changes to the EEPROM
|
