containerd/api
Stephen J Day ebd96a19d3
api: lock down api for 1.1 release
While there were no changes to the core API for the 1.1 release, we
still need to lock down the 1.1 version of the API to follow the
process.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2018-04-02 11:56:40 -07:00
..
events Regenerate protos with Go 1.10, and make check conditional 2018-02-21 10:51:43 +01:00
services Regenerate protos with Go 1.10, and make check conditional 2018-02-21 10:51:43 +01:00
types Licence header added 2018-02-19 10:32:26 +09:00
1.0.pb.txt api: lock down 1.0 API descriptors 2017-12-05 13:17:08 -08:00
1.1.pb.txt api: lock down api for 1.1 release 2018-04-02 11:56:40 -07:00
next.pb.txt rename snapshot->snapshots proto pkg and service 2017-11-29 14:55:24 -08:00
README.md Minor typo fix. 2017-08-10 06:23:21 +00:00

This directory contains the GRPC API definitions for containerd.

All defined services and messages have been aggregated into *.pb.txt descriptors files in this directory. Definitions present here are considered frozen after the release.

At release time, the current next.pb.txt file will be moved into place to freeze the API changes for the minor version. For example, when 1.0.0 is released, next.pb.txt should be moved to 1.0.txt. Notice that we leave off the patch number, since the API will be completely locked down for a given patch series.

We may find that by default, protobuf descriptors are too noisy to lock down API changes. In that case, we may filter out certain fields in the descriptors, possibly regenerating for old versions.

This process is similar to the process used to ensure backwards compatibility in Go.