1# Versioning and Releases
2
3Note: This document references terminology defined at http://semver.org.
4
5## Release Frequency
6
7Regular MINOR releases of gRPC-Go are performed every six weeks. Patch releases
8to the previous two MINOR releases may be performed on demand or if serious
9security problems are discovered.
10
11## Versioning Policy
12
13The gRPC-Go versioning policy follows the Semantic Versioning 2.0.0
14specification, with the following exceptions:
15
16- A MINOR version will not _necessarily_ add new functionality.
17
18- MINOR releases will not break backward compatibility, except in the following
19circumstances:
20
21 - An API was marked as EXPERIMENTAL upon its introduction.
22 - An API was marked as DEPRECATED in the initial MAJOR release.
23 - An API is inherently flawed and cannot provide correct or secure behavior.
24
25 In these cases, APIs MAY be changed or removed without a MAJOR release.
26Otherwise, backward compatibility will be preserved by MINOR releases.
27
28 For an API marked as DEPRECATED, an alternative will be available (if
29appropriate) for at least three months prior to its removal.
30
31## Release History
32
33Please see our release history on GitHub:
34https://github.com/grpc/grpc-go/releases
View as plain text