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

Branch cleanup #1

Open
g-scott-murray opened this issue Oct 8, 2021 · 2 comments
Open

Branch cleanup #1

g-scott-murray opened this issue Oct 8, 2021 · 2 comments

Comments

@g-scott-murray
Copy link

Now that the repository has been migrated here for future development, I propose the following cleanup:

  • The "AGL" branch be renamed to "dunfell" (or a new "dunfell" branch be forked from it). This would better match OE/Yocto community branch layout expectations.
  • The "master" branch be renamed to "main" (or potentially "dev", etc.) and the "AGL"/"dunfell" branch changes merged into it, or alternatively the current "master" be replaced with a new "main" branch off of the "AGL"/"dunfell" branch (and the existing "master" deleted). Dropping the "master" naming seems worthwhile to match what the wider FOSS community is moving to, and we need to establish a new baseline for tracking upstream OE/Yocto development (e.g. the syntax override changes in 3.4/honnister).
  • All other branches be removed. They all seem not interesting at this point IMO, and if this new location is intended to be a ongoing maintained source, dropping the 5-6 year old experiment/feature branches to avoid clutter seems worthwhile.
@keplersj
Copy link

keplersj commented Nov 2, 2022

I think all of these changes make a lot of sense. I've made some changes locally to support the Hardknott version of Yocto and would like to get these upstreamed. What would be the best path to getting branches set up in the OpenEmbedded style (a branch for each yocto major release)?

@keplersj
Copy link

keplersj commented Nov 3, 2022

@jjardon Are you or someone else responsible for this repository?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants