Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DTP Plug-in Versioning Policy"
(New page: ==Status== [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. ==Introduction== This document specifies plug-in version...) |
|||
| Line 3: | Line 3: | ||
==Introduction== | ==Introduction== | ||
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 [[Version Numbering | 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. | 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 [[Version Numbering | 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. | ||
| + | ==Definitions== | ||
| + | *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. | ||
| + | ==Policy== | ||
| + | * 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. | ||
Revision as of 12:15, 29 October 2007
Contents
Status
[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.
Introduction
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.
Definitions
- 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.
Policy
- 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.