Ionic Framework follows the Semantic Versioning (SemVer) convention:
major.minor.patch. Incompatible API changes increment the
major version, adding backwards-compatible functionality increments the
minor version, and backwards-compatible bug fixes increment the
A major release will be published when there is a breaking change introduced in the API. Major releases will occur roughly every 6 months and may contain breaking changes. Several release candidates will be published prior to a major release in order to get feedback before the final release. An outline of what is changing and why will be included with the release candidates.
A minor release will be published when a new feature is added or API changes that are non-breaking are introduced. We will heavily test any changes so that we are confident with the release, but with new code comes the potential for new issues. We are scheduled to release a minor version every 6 weeks, if any features or API changes were made.
A patch release will be published when bug fixes were included, but the API has not changed and no breaking changes were introduced. We are scheduled to release a new patch version every week, but there may be times where we need to release sooner or later than scheduled. To ensure patch releases can fix existing code without introducing new issues from the new features, patch releases will always be published prior to a minor release.
To see a list of all notable changes to Ionic please refer to the changelog. This contains an ordered list of all bug fixes and new features under each release.