|Re: [cross-project-issues-dev] DTP major version bump for Neon|
----- Original message -----
From: Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
To: Ed Willink <ed@xxxxxxxxxxxxx>, "cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] DTP major version bump for Neon
Date: Wed, Oct 28, 2015 9:45 AM
I gave the justification several times. You are choosing to disregard it. Java API is not bundleâs sole API. I donât consider a restriction in requirements a compatible change. DTP 2 is certainly not a drop-in replacement for DTP 1.12 and the version numbering truthfully communicates that fact.
I understand the temptation to fudge the truth when it comes to version numbers, but that doesnât make it a sound engineering practice.
On 28/10/2015 13:13, Konstantin Komissarchik wrote:
I have no specific plans re ODAâs Java API.
So absolutely no justification for a change then. There is no need for all plugins to bump together. It is cosmetically nice to see all plugins with the same version, but it just isn't tenable long term.
For instance many OCL plugins remain at 3.x although those that have been affected by UML major changes have moved to 4.x and 5.x.
Inflicting a major change on clients is not a bit of a pain, it is a major pain, particularly for those clients that are stable and consequently have minimal maintenance teams. In some cases useful but unmaintained tools, such as UML2 Tools, are killed by the major version change.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit