-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
designSomething needing thoughtSomething needing thoughtopen to discussionOpen to thoughts and opinionsOpen to thoughts and opinions
Description
How this is versioned will eventually need some thought. For now it's simply split between two branches
master
for zig master (currently 0.15-dev)0.14.x
for zig 0.14 latest (currently 0.14.1)
with zlinter remaining at 0.0.1
in its build.zig.zon
between changes being submitted (regardless of whether there are breaking changes). Development simply occurs branched from one of these and commits are cherrypicked across as changes aim to be zig version agnostic.
A downside to this is there is no linter specific version metadata attached to the version so you may get an updated version between calling zig fetch
without what changed being super obvious
Some open questions:
- Version in GitHub with releases, tags or branches?
- Should the version in Github differ from zig build zon? (e.g., zon could be base
0.1.2
and GitHub could be a build number or timestamp or commit)
Metadata
Metadata
Assignees
Labels
designSomething needing thoughtSomething needing thoughtopen to discussionOpen to thoughts and opinionsOpen to thoughts and opinions