You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I understood so far, the build scripts are the only relevant files in this repository, and the final framework are only taking these files.
Is it normal that there is only v3.4-branch present in this repo and I should understand that builds scripts are identical for 3.5, 3.6 and 3.7 ?
I would like to propose a backport of the PR we've just merged #23 for v3.X but I'm not sure how to proceed should I propose it for v3.4 branch and it will also affect v3.6 for instance ?
(our project is currently based on v3.X that's why...)
The text was updated successfully, but these errors were encountered:
I would like to propose a backport of the PR we've just merged #23 for v3.X but I'm not sure how to proceed should I propose it for v3.4 branch and it will also affect v3.6 for instance ?
We usually maintain only the latest stable version of Zephyr, without backporting new functionality to previous versions (except for critical bug fixes). Additionally, the changes in #23 can be considered as breaking, since they may affect older PlatformIO projects that have west.yml in the root folder, which developers do not expect to be processed.
As a workaround, you can try using an extra script that applies a patch to the framework files (see docs).
Hi,
From what I understood so far, the build scripts are the only relevant files in this repository, and the final framework are only taking these files.
Is it normal that there is only v3.4-branch present in this repo and I should understand that builds scripts are identical for 3.5, 3.6 and 3.7 ?
I would like to propose a backport of the PR we've just merged #23 for v3.X but I'm not sure how to proceed should I propose it for v3.4 branch and it will also affect v3.6 for instance ?
(our project is currently based on v3.X that's why...)
The text was updated successfully, but these errors were encountered: