You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 2, 2020. It is now read-only.
@phax commented in #55 that Schematron should use semantic versioning for releases.
I agree that semantic versioning should be used.
The current single release -- https://github.com/Schematron/schematron/releases/tag/2017-02-09 -- exists because we needed a baseline against which later changes can be compared. It is tagged with a date because @rjelliffe is the only one with the meritocracy level to say what the Schematron version number should be.
The text was updated successfully, but these errors were encountered:
Yes. The issue goes beyond versioning: should we have separate distros and code bases for xslt1, 2 and 3 engines? That would allow the XSLT 2 & 3 versions to be single scripts not a pipeline.
@phax commented in #55 that Schematron should use semantic versioning for releases.
I agree that semantic versioning should be used.
The current single release -- https://github.com/Schematron/schematron/releases/tag/2017-02-09 -- exists because we needed a baseline against which later changes can be compared. It is tagged with a date because @rjelliffe is the only one with the meritocracy level to say what the Schematron version number should be.
The text was updated successfully, but these errors were encountered: