[eclipse-dev] Version numbering reminder

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

As we prepare to fork for development
of 3.2.1 and 3.3, it is important to keep in mind the policy on evolution
of version numbers.  For complete details, refer to:

http://www.eclipse.org/equinox/documents/plugin-versioning.html

Here is a brief summary:

3.2.0 stream
 - If further 3.2.0 builds are
required before final release, DO NOT change the major/minor/service segments

3.2.1 stream
 - On first contribution to this
stream, increment the service segment by one from the number in  the
3.2 release.  For example, if your plugin was number 1.0.0, it should
become 1.0.1.  3.1.100 becomes 3.1.101.
 - API is frozen in 3.2.1, so changes
to major/minor numbers are not required

3.3 stream
 - In the first build of this stream
(HEAD), either major, minor, or service segment must be incremented from
the number in the 3.2 release, depending on the nature of the change:
    - Bug fix only: increment
service segment by 100.  (e.g., 1.0.0 -> 1.0.100.  3.1.100
-> 3.1.200).
    - New API or significant
change: increment minor segment by one, and reset service segment to zero.
(e.g., 1.0.0 -> 1.1.0.  3.1.100 -> 3.2.0)
    - Breaking API change:
increment major number by one and reset minor and service numbers to zero.

Generally, the version number of a plugin
only needs to change once during a release cycle.  Multiple changes
may be required if you initially only make bug fixes, and then later decide
to add new API. (for example, change from 3.2.0 to 3.2.100, and then decide
to move to 3.3.0).

Version number prerequisites:  In
your manifest.mf, you specify the allowable version range of plugins you
require.  Generally, NO change is required to these ranges for most
plugins.  Most plugins allow a range up to, but not including, the
next major number.  If you begin to use new API introduced by your
prerequisite, you will need to increment the lower bound on this range
to match the version in which new API was introduced.

Feature version numbers: Changes to
feature version numbers will be coordinated with runtime/releng.  Most
developers don't need to worry about feature version numbers.

John & Pascal (version number police)