Skip to main content
Jump to: navigation, search

DTP Plug-in Versioning Policy


[10/29/07]: This document is a draft. It has not been approved by the DTP PMC and should not be taken as DTP policy.


This document specifies plug-in versioning rules for DTP. That is, a policy for changing plug-in version numbers based on the types of changes made to the plug-in is specified below. We follow generally accepted Eclipse rules in this area, for example the versioning policy for the Eclipse platform. It is important that all DTP committers adhere to this policy so tools (such as Eclipse Update Manager) and DTP users can determine the types of changes present between two versions of a given plug-in.


  • A DTP plug-in version number has four fields, separated by a ".": Major.Minor.Service.Qualifier
  • A major change indicates breakage in API or significant new/reorganization of functionality.
  • A minor change indicates changes visible to users or extenders of DTP.
  • A service change indicates bug fixes.
  • A qualifier change indicates the plug-in has changed.


  • The major, minor, and service fields respectively are to be updated once per DTP stream release cycle, depending on the type of change as described above.
  • The qualifier field is to be updated whenever anything in CVS for the plug-in is changed.

Back to the top