Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update for release branch or LTS and conform to the Zephyr example application #69

Open
cfriedt opened this issue Oct 20, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@cfriedt
Copy link
Owner

cfriedt commented Oct 20, 2021

The Zephyr example application is the authority for how Zephyr modules should be organized.

Additionally, with the release of v2.7.0 (LTS2), we should change which rev we point to.

It would also make sense to adopt a similar tagging convention for tagged releases.

E.g. update west.yml to point at v2.7.0, tag v2.7.0, and and then update west.yml to point at main

When v2.7.1 is tagged, similarly, we should update.

@cfriedt cfriedt added the enhancement New feature or request label Oct 20, 2021
@cfriedt cfriedt self-assigned this Oct 20, 2021
@cfriedt
Copy link
Owner Author

cfriedt commented Aug 11, 2022

Probably will not be upgradeable on v2.7 branch due to additional requirements that will not be backported.

Updating this issue to reflect that we should be pinning to releases (ideally LTS)

@cfriedt cfriedt changed the title update for v2.7.0 and conform to the Zephyr example application update for release branch or LTS and conform to the Zephyr example application Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant