From 2a3451efac3f385e9004f5c817ffa672c778f92d Mon Sep 17 00:00:00 2001 From: hsaif Date: Fri, 21 Aug 2026 17:02:33 +0200 Subject: [PATCH 1/3] docs: Update Versions file to update communication about releases --- VERSIONS.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/VERSIONS.md b/VERSIONS.md index 0bee3a11b..84e567444 100644 --- a/VERSIONS.md +++ b/VERSIONS.md @@ -9,11 +9,17 @@ When a new feature set comes online or a small breaking change is introduced, th The MAJOR version is used to indicate the family of technology represented by the library. Breaking changes that require extensive reworking of code will cause the MAJOR version to be incremented by one, and the MINOR and PATCH versions will be reset to zero. Since frequent major updates can be very disruptive, we will only introduce this type of breaking change when absolutely necessary. -New MAJOR versions will be communicated in advance via: +## Support lifecycle -* Box SDK documentation, such as API reference documentation, user guides, SDK product marketing pages, and GitHub readme(s) are updated to indicate the campaign timeline and provide guidance on upgrading affected applications. +Each Box SDK README publishes a **[Version schedule](README.md#version-schedule)** table. That table is the source of truth for which **major versions** are **Supported**, when each was first released, and when each reaches **end of life (EOL)**. * Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. +After a major version reaches EOL it no longer receives new features, bug fixes, or security patches. Existing applications that pin that version continue to run, but you should plan to upgrade. The version is then marked `EOL` in the README schedule. + +Major version releases, breaking changes, and EOL dates are announced through public channels via: + +Box developer documentation, such as the API reference, user guides, and GitHub READMEs. + Deprecations are introduced in minor releases. We will not introduce new deprecations in patch releases. These deprecations will preserve the existing behaviour while emitting a warning that provide guidance on: * How to achieve similar behaviour if an alternative is available From d13019d1f9b9a40858ce964e0e0f16a9ed135649 Mon Sep 17 00:00:00 2001 From: hsaif Date: Fri, 21 Aug 2026 17:07:42 +0200 Subject: [PATCH 2/3] docs: Update Versions file to update communication about releases --- VERSIONS.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/VERSIONS.md b/VERSIONS.md index 84e567444..be3481d70 100644 --- a/VERSIONS.md +++ b/VERSIONS.md @@ -12,13 +12,14 @@ The MAJOR version is used to indicate the family of technology represented by th ## Support lifecycle Each Box SDK README publishes a **[Version schedule](README.md#version-schedule)** table. That table is the source of truth for which **major versions** are **Supported**, when each was first released, and when each reaches **end of life (EOL)**. -* Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. After a major version reaches EOL it no longer receives new features, bug fixes, or security patches. Existing applications that pin that version continue to run, but you should plan to upgrade. The version is then marked `EOL` in the README schedule. Major version releases, breaking changes, and EOL dates are announced through public channels via: -Box developer documentation, such as the API reference, user guides, and GitHub READMEs. +- Box developer documentation, such as the API reference, user guides, and GitHub READMEs. + +- Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. Deprecations are introduced in minor releases. We will not introduce new deprecations in patch releases. These deprecations will preserve the existing behaviour while emitting a warning that provide guidance on: From f49c44ce0ccfc9394ae7c48209e04ca35f00a4e5 Mon Sep 17 00:00:00 2001 From: hsaif Date: Fri, 21 Aug 2026 17:09:37 +0200 Subject: [PATCH 3/3] docs: Update Versions file to update communication about releases --- VERSIONS.md | 1 - 1 file changed, 1 deletion(-) diff --git a/VERSIONS.md b/VERSIONS.md index be3481d70..9f5a62c0f 100644 --- a/VERSIONS.md +++ b/VERSIONS.md @@ -18,7 +18,6 @@ After a major version reaches EOL it no longer receives new features, bug fixes, Major version releases, breaking changes, and EOL dates are announced through public channels via: - Box developer documentation, such as the API reference, user guides, and GitHub READMEs. - - Deprecation warnings are added to the SDKs, outlining the path to end-of-support and linking to the SDK documentation. Deprecations are introduced in minor releases. We will not introduce new deprecations in patch releases. These deprecations will preserve the existing behaviour while emitting a warning that provide guidance on: