Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[DISCUSSION] Deprecate support for CycloneDX schema version 1.0 #157

Closed
madpah opened this issue Feb 2, 2022 · 1 comment
Closed

[DISCUSSION] Deprecate support for CycloneDX schema version 1.0 #157

madpah opened this issue Feb 2, 2022 · 1 comment

Comments

@madpah
Copy link
Collaborator

madpah commented Feb 2, 2022

As called out in #151 by @jkowalleck, 1.0 is old and very sparse compared to the more recent versions of the CycloneDX schema.

This ticket aims to collect any feedback from the community as to whether:

  • This library is used to product BOMs in schema version 1.0
  • Anyone has any strong feelings / requirements for us to keep supporting 1.0
@jkowalleck
Copy link
Member

jkowalleck commented Feb 2, 2022

yes, this "feature" would cause breaking changes, as it cuts of an existing feature, and might remove existing classes/structures.

benefit: removing 1.0 capabilities removed complexity from the normalizers as no code-branching for is required, for features that exist from spec 1.1 on.

@CycloneDX CycloneDX locked and limited conversation to collaborators Apr 20, 2022
@madpah madpah converted this issue into discussion #217 Apr 20, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants