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

Upgrade CI/CD to Saxon10 for XSLT support #1035

Closed
3 tasks
wendellpiez opened this issue Oct 5, 2021 · 0 comments · Fixed by #1187
Closed
3 tasks

Upgrade CI/CD to Saxon10 for XSLT support #1035

wendellpiez opened this issue Oct 5, 2021 · 0 comments · Fixed by #1187

Comments

@wendellpiez
Copy link
Contributor

User Story:

An an open-source library Saxon9 should be useful for the indefinite future, however the current version Saxon10 is more performant and offer better (tighter) compile-time checks, for example.

Goals:

Let's upgrade Saxon9 to Saxon10 throughout the CI/CD pipelines. The invocation syntax is the same, so this mostly means integration and testing. Any newly discovered bugs in running code should be repaired etc.

As a follow-on task: references to Saxon9 throughout documentation (readmes) should be updated to say Saxon10.

(This was prompted by #1027.)

Dependencies:

None known.

Acceptance Criteria

  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}

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

Successfully merging a pull request may close this issue.

2 participants