[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3462:
---------------------------------------
The approaches for this look like:
-Change the version field to a string rather than an integer, and allow for the break in
backwards compatibility.
- Add major/minor/micro version as fields and deprecate the version integer (make it just
the major version) and try to retain some compatibility. Although we would need to add
duplicate admin methods ect. to allow for the full version to be specified.
- Use a property to drive whether the version is encoded for example 10 bits for each part
with some alternative logic for displaying the version.
The first is by far the simplest and the reason for pushing this to 9.0, but if anyone
wants to make the case for a more backwards compatibly scenario, let me know.
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)