...

Release Numbering Convention

With DSpace 3.0, the DSpace Developers will be changing our release numbering scheme. Release numbers will now only consist of two numbers: {{\[major\].

\[minor\]}} (e.g.

 3.

• Increment major (e.g. 1.x.x -> 2.x.x) for major architectural changes
• Increment minor (e.g. 1.7.x -> 1.8.x) for feature changes and minor architectural changes (database schema, translations, APIs may change, though we'll try and keep API changes as small as possible, and will always provide an upgrade/migration path)
• Increment subminor (e.g. 1.7.0 -> 1.7.1) for bug-fix only releases (database, translations and core APIs stable)

...

0, 3.1, 4.0):

• Major Releases: incrementing the first number ('major') will represent a new MAJOR release of DSpace. A major release may include any or all of the following: new features, system improvements, architectural changes, bug fixes. All major releases end in ".0", so "3.0", "4.0", and "5.0" would all represent major releases.
• Minor (Bug-Fix) Releases: incrementing the second number ('minor') will represent a new MINOR release of DSpace. A minor release will only include bug fixes to an existing major release. For example, "3.1" and "3.2" would represent two minor releases which only include bug fixes to the "3.0" major release..

For more information see DSpace Release Numbering Scheme and the initial DSpace 3.0 Announcement

The one exception is that the Language Packs ({{dspace-api-lang}} and {{dspace-xmlui-lang}}) use the numbering convention {{\[major\].\[minor\].\[sequence-number\]}} (e.g. 3.0.0, 3.0.1, 3.1.0, etc.).  This allows us to release new versions of the language packs more frequently than normal DSpace releases, as needed.

Prerequisites

Verify Release Privileges

...