Merge pull request kubernetes#3 from kubernetes/master

Update 4/24/18 release notes

release-process-documentation/release-team-guides/release-lead.md

@@ -118,7 +118,7 @@ A guiding principle for the lead is be an arbiter of decisions, and not the prim
     <td>4</td>
     <td><p>- Assist the features lead with anything required for feature freeze
 <p>- Remind the community about feature freeze
-<p>- Bring exceptions to to the Release Team meetings, and make sure SIG representatives for the exception(s) know to attend and discuss if necessary
+<p>- Bring exceptions to the Release Team meetings, and make sure SIG representatives for the exception(s) know to attend and discuss if necessary
 <p>- Make sure everything is in synch between the features repo and the features tracking spreadsheet
 <p>- If there are features with questions or concerns, help coordinate those conversations between the team and the SIG/owners
 <p>- Start collecting SIG release themes in the release notes draft, outlining what they are delivering this release milestone, and how it aligns with their mission statements - start with SIGs identifying features in the features repo, and focus on those since not every SIG will be delivering something</td>

releases/release-1.11/release-1.11.md

@@ -9,6 +9,7 @@
 * [Feature Tracking Sheet](http://bit.ly/k8s111-features)
 * [Milestone Process](https://github.com/kubernetes/community/blob/master/contributors/devel/release/issues.md)
 * [Meeting Minutes](http://bit.ly/k8s111-minutes)
+* [CI Signal Report](http://bit.ly/k8s111-cisignal)
 * [Retrospective Document](http://bit.ly/k8s111-retro)
 
 **tl;dr** The 1.11 release cycle begins on **Tuesday, April 3rd, 2018**, and ends on release day, **Tuesday, June 26th**.  Feature freeze is **Tuesday, April 24th**.  Code freeze begins **Monday, May 28th** and ends **Tuesday, June 19th**, but [may be shortened](#conditionally-shortening-code-freeze) and begin later. Docs must be completed and reviewed by **Friday, June 11th**.