Overview

Stability ensures that reusable components and libraries, tutorials, tools, and learned practices don't become obsolete unexpectedly. Stability is essential for the ecosystem around Abyss to thrive.

This document contains the practices that are followed to provide you with a leading-edge UI library, balanced with stability, ensuring that future changes are always introduced in a predictable way.

Semantic Versioning

Abyss follows Semantic Versioning 2.0.0. Abyss version numbers have three parts: major.minor.patch. The version number is incremented based on the level of change included in the release.

• Major releases contain significant new features, some but minimal developer assistance is expected during the update. When updating to a new major release, you may need to run update scripts, refactor code, run additional tests, and learn new APIs.
• Minor releases contain important new features. Minor releases should be fully backward-compatible; no developer assistance is expected during update, but you can optionally modify your apps and libraries to begin using new APIs, features, and capabilities that were added in the release.
• Patch releases are low risk, contain bug fixes and small new features. No developer assistance is expected during update.

version2.0.0.

v

2.

Major version: increment for breaking changes

2

.

0.

Minor version: increment for new features

0

.

0.

Patch version: increment for bug fixes

0

Release Frequency

A regular schedule of releases helps you plan and coordinate your updates with the continuing evolution of Abyss. In general, you can expect the following release cycle:

• A major release typically every year for major changes.
• A minor releases every two weeks after each sprint.
• A patch release at any time for urgent bugfixes.

Deprecation Practices

Sometimes "breaking changes", such as the removal of support for select APIs and features, are necessary.

To make these transitions as easy as possible:

• The number of breaking changes is minimized, and migration tools provided when possible.
• The deprecation policy described below is followed, so that you have time to update your apps to the latest APIs and best practices.

Deprecation Policy

• Deprecated features are announced in the changelog, and when possible, with warnings at runtime.
• When a deprecation is announced, recommended update path is provided.
• Existing use of a stable API during the deprecation period is supported, so your code will keep working during that period.
• Peer dependency updates (React) that require changes to your apps are only made in a major release.

Tested React Native versions

Abyss Versions	Tested React Native Version	Tested Architecture
		New	Old
>= 1.65.0	v0.76.6
<= 1.64.0	v0.71.14