You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
alilleybrinker opened this issue
Sep 20, 2023
· 0 comments
Labels
c-policyCategory: Project policy outside of the content of the specification itself.c-specCategory: Improvements or additions to the OmniBOR specification
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.
The text was updated successfully, but these errors were encountered:
alilleybrinker
changed the title
Specification Versioning
Implement active versioning / version bumping of the specification
Sep 20, 2023
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
c-policyCategory: Project policy outside of the content of the specification itself.c-specCategory: Improvements or additions to the OmniBOR specification
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.
The text was updated successfully, but these errors were encountered: