-
Notifications
You must be signed in to change notification settings - Fork 96
version number, take 2 #2599
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
base: dev
Are you sure you want to change the base?
version number, take 2 #2599
Conversation
for actual use, yet — in large part untested, and prose not written. This version is simply for Council to see if they like it.
solves the problem for which the original ticket was opened, IIRC).
|
All tests pass on my local system (Padfoot, not in the Docker). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs a new remarks element explaining that its content can be one of four different formats of version, and perhaps pointing to the definitions of the dataSpecs. It's going to be quite challenging to figure out which specific dataSpec you're not quite aligning with when you get error messages typing a version string.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, although I have no intention of putting in that effort until Council approves the general approach.
…e of teidata.duration.iso & teidata.version
…after manual merge of application and att.styleDef
solves the problem for which the original ticket was opened, IIRC).
For the moment this branch is a partiallly working version of version sublcasses that is NOT ready for actual use, yet — in large part untested, and prose not written. This version is simply for Council to see if they like it, but (I think) it does address the problem for which original ticket was open.