Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dtp-dev] DTP plugin version change to minor increment only

FYI, I am changing the DTP plugin versions to increment the minor segment only, rather than the major segment.  The version major segment change was unnecessary given what has changed in DTP and has too much impact on the DTP clients.

This reflects the clear version numbering guidance given here:  Here is the relevant section:

- - - - - - - - - - - - -
When to change the minor segment

The minor segment number must be incremented when a plug-in changes in an "externally visible" way. Examples of externally visible changes include binary compatible API changes, an updated BREE(Bundle-RequiredExecutionEnvironment), significant performance changes, major code rework, etc. Another way to know when this version number should be changed is by exclusion: it should indicate changes that are neither bug fixes (indicated by the service segment) nor breaking API changes (indicated by the major segment). When the minor segment is changed, the service segment is reset to 0.

Example: From the version 2.2.7, a minor change would lead to 2.3.0.
- - - - - - - - - - - - -

So the change to Java 8 implies a minor segment change.


Brian Payton

Developer Tooling for Data Services
IBM Silicon Valley Laboratory

Back to the top