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

Implement active versioning / version bumping of the specification #58

Open
alilleybrinker opened this issue Sep 20, 2023 · 0 comments
Open
Labels
c-policy Category: Project policy outside of the content of the specification itself. c-spec Category: Improvements or additions to the OmniBOR specification

Comments

@alilleybrinker
Copy link
Member

Right now, the specification is under heavy editing, and is perpetually at version 0.1. That said, it may be better to actually handle bumping the version of the spec when changes are made to it. Given that it's pre-1.0, any changes to the spec would constitute a minor version bump. This at least lets us be more concrete about referring to changes in the spec as it continues to evolve.

I'd also argue that changes to any of the annexes be considered as a change to the overall spec, necessitating a version bump. Ideally, new versions would also be tagged.

@alilleybrinker alilleybrinker changed the title Specification Versioning Implement active versioning / version bumping of the specification Sep 20, 2023
@alilleybrinker alilleybrinker added c-spec Category: Improvements or additions to the OmniBOR specification c-policy Category: Project policy outside of the content of the specification itself. labels Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c-policy Category: Project policy outside of the content of the specification itself. c-spec Category: Improvements or additions to the OmniBOR specification
Projects
None yet
Development

No branches or pull requests

1 participant