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

Build a forward looking strategy for trestle to support multiple oscal versions (potentially in the same codebase #1789

Open
2 tasks
butler54 opened this issue Dec 19, 2024 · 2 comments

Comments

@butler54
Copy link
Collaborator

Issue description / feature objectives

Today a bugfix change from NIST triggers a major change for trestle.

In an ideal world trestle versions should be able to support a range of minor and bugfix versions in the same codebase.

Caveats / Assumptions

Completion Criteria

  • Current and forward looking strategy is documented.
  • Issues for code buildout are generated.
@butler54
Copy link
Collaborator Author

One strategy could be to opportunistically upgrade document versions.

@butler54
Copy link
Collaborator Author

Do we need to be able to export at the same level as import or can we assume minor / bugfix oscal version bumps are okay for downstream tools?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New
Development

No branches or pull requests

1 participant