Open junaruga opened 2 years ago
I only exported the code, I can push tags as well, but our bios builds and upstream tags do not align well as there is some overlap.
OK. I agree on not managing the upstream tags on this downstream repository. So, maybe you are managing the downstream, this repository specific tags used on your bios builds, right? I have no experience of developing a firmware. So, I might be wrong. But I suppose that the downstream specific git tags are useful to know the code or commits included in a BIOS version. You might use a downstream unique version string such as "<a-prefix>-v3.02
" to avoid confusing from a upstream tag or just v3.02
or v3.2
.
I'm not certain there's value in any of the upstream tags, honestly. Having tags that align with Framework's releases are the ones that matter, so we can try use a specific release version with one tweak rather than a between-release repo state + that tweak.
I noticed this repository doesn't have any tag info.
I can see the tag info on the upstream chromium ec repository.
I expected there are the tags "v3.2", "v3.6", "v3.7" used to ship BIOS version 3.02, 3.06, 3.07 and etc on this repository. Is the missing git tag info intentional?