Backward-incompatible changes to CockroachDB interfaces. This may include changes to SQL statements,
If the change is considered backward-incompatible (i.e., the change can break programmatic usage of an interface), use the
Changes to CockroachDB features requiring an enterprise license, e.g.,
Changes to cockroach commands and endpoints that affect primarily operators tasked with setting up and maintaining production clusters.
This includes changes to logging configurations and behavior, additions or removal of metrics, health and monitoring endpoints, HTTP endpoints, environment variables, integrations with service managers, CLI flags for server commands, exit codes, etc.
Changes to cockroach commands that affect primarily application developers, CockroachDB developers and contributors, and operators running experiments or small-scale testing/staging clusters.
This includes changes to the SQL shells,
Changes to the DB Console and any associated metrics.
Changes that impacts the use of security features (IAM, TLS, etc.) or the security profile of the product.
Changes that improve performance, often at kv, storage, and SQL engine levels.
Changes that fix known problems as opposed to add or improve functionality.
Changes that don't fit anywhere else. Only use this if you have no other good option. This might include changes to logs and user-facing configs for Kubernetes, Prometheus, Alertmanager, etc. We probably need new, meaningful categories.
Changes to requirements for building CockroachDB from source.