[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3462:
---------------------------------------
Can you give an example here? is like "foo-1.2.3.vdb" where
"foo-1.2.3" is the VDB name, and there is no notion of version. version is/will
be always say "1"?
Yes, and the version field in the vdb.xml will be optional. For full compatibility,
I'll make the revision still apply even if semantic versioning is used - however is of
course redundant.
Another question I have is, how are these handled other data sources,
RDBMS or otherwise? Is this specific only to Teiid? after all all we are saying is this is
a version of metadata/schema?
This just supplants the revision concept for VDBs.
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)