We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As a Metaschema {stakeholder}, I would like to know what is a good commit hash to use in the oscal repo to update the submodule
I would like a release to be tagged of a stable version that I can use upstream in the oscal repo.
create a tagged branch and issue an official release under github
The text was updated successfully, but these errors were encountered:
No branches or pull requests
User Story:
As a Metaschema {stakeholder}, I would like to know what is a good commit hash to use in the oscal repo to update the submodule
Goals:
I would like a release to be tagged of a stable version that I can use upstream in the oscal repo.
Dependencies:
create a tagged branch and issue an official release under github
Acceptance Criteria
The text was updated successfully, but these errors were encountered: