SigMF
SigMF copied to clipboard
sigmf
Rename default branch, resolve versioning
Now that the spec has been separated from the python module, the versions are now separate too. There are a few outstanding issues in this repo that I'd like to resolve that were remnants from the before-times:
- rename default branch from
sigmf-v1.xtomain - rename mis-named tags (
SigMF-v1.0.0) tov1.0.0 - create new release for
v1.2.0. Most recent release isv1.0.0, but most recent tag isv1.1.0. - update the spec example version to match current release
If another maintainer signs off on these changes I can do this myself.
Do we want to move the logo to a separate repo?
I really like the idea of using "main" as the default branch name. I think logo is OK to stay in this repo, although an SVG of the logo would be pretty sweet if anyone can manage that =). I would suggest waiting for the json schema to get merged in before we cut a release, we can bump the version of the json schema along with the title in the markdown at the same time.
I think logo is OK to stay in this repo
It's a .sigmf file as an example where we can keep the metadata up to date w/the spec.
although an SVG of the logo would be pretty sweet if anyone can manage that =)
There are (7) svg versions of the logo in the zip file on this page. I think what you are suggesting is that we add logo-scope-color.svg to the repo, which may make sense since it's the most useful version. When I first added the png, I did that since GitHub wouldn't render an svg in a markdown file, but they added that feature in 2022. I'll make a PR.
As there are no objections I'm going to proceed:
- [x] Renaming the base branch to
mainand tags the appropriate commits for other versions. - [x] Cleanup tags for all versions
- [x] Create a PR that updates the spec to
1.2.0. - [x] Create a PR in sigmf-python for this branch -> now this PR
- [x] Create releases commensurate with tags
- [x] Create PyPi release for sigmf-python