[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3462:
-------------------------------------
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
I am not saying to deprecate current version number, nor I am saying making semantic
version a first class feature, this is optional feature for select "few" users
who want this feature. Disrupting all the other users based on this does not seem like
good idea to me. We do not have clue how user's individual current work flows have
used or not used current version system. Your comment about auto-increment makes logical
sense, I remember from MM days once we tried the auto-increment of the version upon the
deployment and that was failure, because it caused more confusion about what was the
target version number allocated, how that can be communicated to the client etc and
eventually that got removed.
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.
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?
To me this is just a "made up" requirement, that does not really provide any
advantages, the semantic version is always defined by a user and current scheme allows
user in using the current revision in that way if they choose to do it. If you feel
strongly that we need to move this direction, then the only option I would advocate is
changing the version to string field, and leave everything as is, and the semantics of
defining the version to the user completely as you were suggesting in previous comments.
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)