GIMP Release Numbering: Stable vs Development

The GNU Image Manipulation Program (GIMP) distinguishes between stable production releases and development snapshots primarily through its version numbering scheme. By examining the three-part version number, users can immediately identify whether a build is thoroughly tested for everyday production or an experimental snapshot featuring work-in-progress tools and architectural changes.

The Major.Minor.Micro Structure

GIMP follows a versioning format composed of three numbers separated by periods: Major.Minor.Micro (represented generically as X.Y.Z).

  • Major (X): Represents a milestone generation of the software, often accompanying major architectural overhauls, interface redesigns, or foundational toolkit upgrades (such as migrating from GTK+ 2 to GTK 3).
  • Minor (Y): Indicates the stability branch of the software and determines whether a build is stable or experimental.
  • Micro (Z): Designates bug fix releases within a stable branch, or sequential snapshot updates within a development branch.

The Odd-Even Minor Version Rule

The critical distinction between stable releases and development snapshots lies within the minor number:

  • Even Minor Numbers Indicate Stable Releases: When the middle number is even (e.g., 2.8, 2.10, 3.0), the version belongs to a stable branch. These releases are intended for general production use, prioritizing stability, reliability, and backward compatibility.
  • Odd Minor Numbers Indicate Development Snapshots: When the middle number is odd (e.g., 2.9, 2.99, 3.1), the software is part of an unstable development branch. These versions are testing grounds where developers introduce new features, test code refactoring, and gather community feedback.

For instance, versions in the 2.10.x series are stable releases suitable for regular graphic design work. Conversely, builds labeled 2.99.x were pre-release development snapshots leading up to the major GIMP 3.0 release, intended for bug hunters and early adopters rather than mission-critical tasks.

The Role of the Micro Number

The third digit behaves differently depending on whether the branch is stable or experimental:

  • In Stable Branches: An increasing micro number (such as 2.10.32 to 2.10.34) delivers maintenance updates, including security patches, performance improvements, and occasional backported features, without altering existing core workflows.
  • In Development Branches: An increasing micro number (such as 2.99.16 to 2.99.18) represents a new development snapshot or milestone release. These point releases frequently introduce substantial, unpolished changes, API revisions, and experimental features that may still contain known bugs or instability.