[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3462:
---------------------------------------
there is NOTHING we can do to validate the fact that a given minor
version of VDB did follow the rules of semantic versioning
That is generally the case with all semantic versioning. Unless you have a full
regression test suite / spec, you are always implicitly trusting the developers that they
versioned appropriately.
why not we introduce a VDB level property for semantic version, then
map this to the "vdb-version", so in cases where we check version number like
JDBC connection, odbc connection, Teiid can provide alternative/additional ways to connect
using the semantic version. Provide an Admin function to get one version from other. We
can also think about re-working "connection type" based on semantic version.
That is somewhat the effect of what I'm talking about with deprecating the version
number. However it does make things awkward to have both concepts - a version/revision
and a semantic version. Keeping the revision as the primary concept you would expect for
example that a semantic version based deployment would have an option to auto-increment
the old version/revision number. It seems best to move things in the direction of the
semantic version while leaving backwards compatibility initially. What I'm looking at
here from an api perspective is that when the old vdbVersion is >= 1, then we expect
the old behavior of just a simple vdb name, otherwise the vdb name should be the full name
/ semantic version.
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)