Recent Kubernetes releases

53 views
Skip to first unread message

Robert Bailey

unread,
Jul 21, 2016, 5:28:06 PM7/21/16
to kubernetes-dev
Hi,

You may have noticed an uptick in the rate at which we have been cutting releases of Kubernetes over the last week. I'll give a brief overview of the recent releases and why we cut them. We hope to avoid having so many releases in close proximity in the future.

v1.2.6 (Friday, July 15th)
  - Fixed a security issue found by RedHat in the 1.2 branch

v1.3.1 (Sunday, July 17th)
  - This release was exactly the same as v1.3.0 with the above mentioned security issue fixed
  - This release also tested our ability to cut a single change release without pulling in all of the other changes on the release branch (if you look closely, we created a release-1.3.0 branch last week)

v1.3.2 (Sunday, July 17th)
  - Fixed a P0 issue discovered in when running Kubernetes in GCE
  - Also rolled up the security fix and other changes that were on the 1.3 release branch

v1.3.3 (expected Thursday, July 21st)
  - Rollup build from the 1.3 branch fixing another P0 issue running Kubernetes on GCE and multiple fixes for large clusters
  - There were many approved cherry picks that didn't have cherry pick PRs yet which will be in the next patch release

v1.3.4 (expected next week)
  - Will clear as much as possible of the cherry pick backlog for 1.3
  - Targeted for a number of visible storage issues

We are working on improving our test infrastructure to avoid finding P0 bugs *after* cutting a minor release. However, we do expect to occasionally cut extra patch releases as security issues as they are discovered. 

Please feel free to reach out (publicly or privately) if you have any questions or concerns. 

Thanks,
Robby

Fabio Yeon

unread,
Jul 22, 2016, 12:37:02 PM7/22/16
to kubernetes-dev
Just a quick follow up, v.1.3.3 testing had a flake, so we're going to try and cut it today (Fri, July 22nd). 

Thanks.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages