From 2c1c20c823ee0498f36b455249f5c7f7011e4b27 Mon Sep 17 00:00:00 2001 From: Jeremy McCormick Date: Wed, 11 Dec 2024 17:11:58 -0600 Subject: [PATCH] Remove sentence on backward compatibility -- too schema-specific --- CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6aafe6bf..a4810764 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -54,7 +54,6 @@ The following guidelines can be used for incrementing the version: - Different `MINOR` versions are backward compatible. - Different `PATCH` versions are completely compatible. -Compatibility typically implies that a client using an updated version of the schema could work with an older version in the deployed database. These suggestions need not be followed strictly, and there may be exceptions. For instance, some operations which are technically backward-compatible, such as adding a table, should likely trigger a `MAJOR` version increment rather than `MINOR`, as they would constitute an important and significant update, potentially requiring significant changes to client code or APIs.