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

Make statement of change control/versioning #4

Closed
kurtseifried opened this issue Dec 12, 2016 · 1 comment
Closed

Make statement of change control/versioning #4

kurtseifried opened this issue Dec 12, 2016 · 1 comment
Labels
documentation Improvements or additions to documentation Project:json format CVE JSON Data Exchange Format

Comments

@kurtseifried
Copy link
Contributor

We should post an official statement about versioning, e.g. that within a major version (3.x) we will maintain compatibility (e.g. only adding fields), but if we modify fields or drop them we'll need to bump the revision. Essentially if the JSON schema needs a change then we should increment the major version number (e.g. 3 to 4).

@csj0 csj0 added Project:json format CVE JSON Data Exchange Format documentation Improvements or additions to documentation labels May 24, 2018
@mprpic
Copy link
Collaborator

mprpic commented Mar 5, 2024

This issue is being closed as obsolete. If you feel it is still relevant to any currently running AWG initiatives, feel free to re-open it or open a new issue. Thank you!

@mprpic mprpic closed this as not planned Won't fix, can't repro, duplicate, stale Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Project:json format CVE JSON Data Exchange Format
Projects
None yet
Development

No branches or pull requests

3 participants