Currently, we distribute libmongocrypt binaries to Linux customers via distro-specific package managers, with a dedicated repository for each minor version tag. Administrators must manually configure their systems to use the repository corresponding to their desired minor version.

This approach has significant operational overhead:

• High maintenance burden: We maintain (# minor releases) × (# supported distros) repositories.
• Frequent documentation updates: Each minor release requires corresponding updates to installation guides.
• No automated upgrades: Customers cannot easily move between minor versions, delaying access to security and bug fixes.
• Complex patching: Critical fixes must be backported across multiple minor versions.

To improve the administrator experience and reduce operational complexity, we should consolidate into a single repository per supported Linux distro.

Proposed changes:

• Maintain one repository per distro.
• Include all minor releases of libmongocrypt within each repository.
• Document how to enable and use the unified repository on each supported platforms.
• Optionally document how versions may be pinned (e.g., libmongocrypt=1.15.*) on supported package managers, if version-specific installation is a desired practice.
• For future ABI-breaking changes, introduce a new major-versioned package (e.g., libmongocrypt2-dev) under the same repository.

As support for older distros ends, we will deprecate and retire per-minor-version repositories, encouraging migration to the unified channel.

This shift reduces maintenance, and enables seamless updates for our users.