|Re: [dtp-dev] DTP plugin version change to minor increment only|
Will this be done for Neon M3?
- Carl Anderson
WTP Releng project lead
Brian Payton---11/05/2015 02:06:09 PM---FYI, I am changing the DTP plugin versions to increment the minor segment only, rather than the maj
From: Brian Payton/Santa Teresa/IBM@IBMUS
To: DTP development mailing list <dtp-dev@xxxxxxxxxxx>
Date: 11/05/2015 02:06 PM
Subject: [dtp-dev] DTP plugin version change to minor increment only
Sent by: dtp-dev-bounces@xxxxxxxxxxx
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.
DTP PMC Lead
Developer Tooling for Data Services
IBM Silicon Valley Laboratory
dtp-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top