-
Notifications
You must be signed in to change notification settings - Fork 10.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add gRPC release schedule document #17306
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few minor nits..
@@ -0,0 +1,22 @@ | |||
# gRPC Release Schedule |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: should this document rather live in grpc.io repository?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this directory gets more eyes from users. We will link to this from the FAQ section in grpc.io.
doc/grpc_release_schedule.md
Outdated
|
||
Below is the release schedule for gRPC [Java](https://github.com/grpc/grpc-java/releases), [Go](https://github.com/grpc/grpc-go/releases) and [Core](https://github.com/grpc/grpc/releases) and its dependent languages C++, C#, Objective-C, PHP, Python and Ruby. | ||
|
||
Releases are scheduled every six weeks on Tuesdays on a best effort basis. In some unavoidable situations a release may be delayed or a language may skip a release altogether and do the next release to catch up with other languages. See the past releases in the links above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: it may be good to interesting to mention the motivation behind six-weekly release schedule (e.g. good balance of delivering new features and fixes quickly to the users and not having too much release overhead, and explaing why we chose fixed release schedule over variable one)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Don't want to make it too verbose so skipped the rationale for fixed vs. variable release.
|
|
|
|
|
|
|
@jtattermusch, any other suggestions? |
Not including actual release dates for ease of maintenance. Will be linking to this doc from other repos and grpcio FAQ.