[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3462:
---------------------------------------
This I like, but my argument is why not push them towards a 3 or 6
digit number in version, which gives same features without any changes?
An encoded version is somewhat limiting in numeric range and does not support qualifiers,
so it's not quite the same feature wise and does require some additional metadata for
backwards compatibility.
To me this is just a "made up" requirement, that does not
really provide any advantages
I don't agree. The current notion of vdb version is really a revision and makes more
sense as a internal construct. To promote something that is part of the api or connection
level around a version should be more general / aligned to user concepts of versioning.
So I think what will come out of this is that the notion of a semantic version will be
part of the vdb name and that the old vdb version / revision will stick around for a while
for backwards compatibility and be optional. It looks like the changes to do that will be
minimally scoped.
Add support for semantic versioning of VDBs
-------------------------------------------
Key: TEIID-3462
URL:
https://issues.jboss.org/browse/TEIID-3462
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.7
Reporter: Marc Shirley
Assignee: Steven Hawkins
Fix For: 9.0
Semantic versioning [1] should be supported in the VDB versioning in order to be able to
easier determine whether there are breaking changes from the client perspective and to
more easily establish a link between client software versions and the VDBs they rely
upon.
[1]
http://semver.org/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)