Skip to content
This repository has been archived by the owner on Nov 2, 2020. It is now read-only.

Schematron releases should use semantic versioning #62

Open
tgraham-antenna opened this issue Feb 12, 2018 · 2 comments
Open

Schematron releases should use semantic versioning #62

tgraham-antenna opened this issue Feb 12, 2018 · 2 comments
Labels
infrastructure Housekeeping

Comments

@tgraham-antenna
Copy link
Member

@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.

@phax
Copy link

phax commented Feb 12, 2018

Great - sounds good :) What does "meritocracy level" mean?

@rjelliffe
Copy link
Member

rjelliffe commented Feb 12, 2018

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.

@tgraham-antenna tgraham-antenna added the infrastructure Housekeeping label Feb 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
infrastructure Housekeeping
Projects
None yet
Development

No branches or pull requests

3 participants